| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
interface LegionInternalsPageHandler {Does this interface work for you or should we define this differently?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
string defaultUrl;should we also send API Key separately or it will be included in this URL?
Sending and displaying URL + API Key might be less error-prone for a user and they won't need to figure out in which format they should concatenate both
interface LegionInternalsPageHandler {Does this interface work for you or should we define this differently?
I think for PoC it works.
SendRequest(string request) => (string response);How do we propagate errors?
mojo::PendingReceiver<legion_internals::mojom::LegionInternalsPageHandler>nit: same, check headers
mojo::PendingReceiver<legion_internals::mojom::LegionInternalsPageHandler>nit: missing header
mojo::PendingReceiver<legion_internals::mojom::LegionInternalsPageHandler>nit: missing header
please check other files.
std::make_unique<LegionInternalsPageHandler>(std::move(receiver));nit: missing header
std::make_unique<LegionInternalsPageHandler>(std::move(receiver));nit: missing header
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
struct LegionInternals {Actually, we might just pass URL + API key as variables and therefore simplify Mojo interface:
https://source.chromium.org/chromium/chromium/src/+/main:docs/webui/webui_in_chrome.md;l=275-277?q=webui%20variable
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
Actually, we might just pass URL + API key as variables and therefore simplify Mojo interface:
https://source.chromium.org/chromium/chromium/src/+/main:docs/webui/webui_in_chrome.md;l=275-277?q=webui%20variable
Done
should we also send API Key separately or it will be included in this URL?
Sending and displaying URL + API Key might be less error-prone for a user and they won't need to figure out in which format they should concatenate both
Done
Oleh LamzinDoes this interface work for you or should we define this differently?
I think for PoC it works.
Acknowledged
SendRequest(string request) => (string response);How do we propagate errors?
I'm not quite sure what's the best approach here. We could just return them as a string "Error: <somemessage>".
mojo::PendingReceiver<legion_internals::mojom::LegionInternalsPageHandler>Christian Dullwebernit: same, check headers
Done
mojo::PendingReceiver<legion_internals::mojom::LegionInternalsPageHandler>nit: missing header
please check other files.
Done
mojo::PendingReceiver<legion_internals::mojom::LegionInternalsPageHandler>Christian Dullwebernit: missing header
Done
std::make_unique<LegionInternalsPageHandler>(std::move(receiver));Christian Dullwebernit: missing header
Done
std::make_unique<LegionInternalsPageHandler>(std::move(receiver));Christian Dullwebernit: missing header
Done
RunTest("legion_internals/legion_internals_test.js", "mocha.run()");I spent a lot of time trying to figure out how to add a simple test but somehow mocha is not found when executing this. I'm not quite sure what's going on but I'd suggest to just submit this and figure out this issue separately
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
RunTest("legion_internals/legion_internals_test.js", "mocha.run()");I spent a lot of time trying to figure out how to add a simple test but somehow mocha is not found when executing this. I'm not quite sure what's going on but I'd suggest to just submit this and figure out this issue separately
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
SendRequest(string request) => (string response);Christian DullweberHow do we propagate errors?
I'm not quite sure what's the best approach here. We could just return them as a string "Error: <somemessage>".
wdyt about returning `{response?: string, error?: string}`?
SendRequest(string request) => (string response);Christian DullweberHow do we propagate errors?
Oleh LamzinI'm not quite sure what's the best approach here. We could just return them as a string "Error: <somemessage>".
wdyt about returning `{response?: string, error?: string}`?
Done
RunTest("legion_internals/legion_internals_test.js", "mocha.run()");Oleh LamzinI spent a lot of time trying to figure out how to add a simple test but somehow mocha is not found when executing this. I'm not quite sure what's going on but I'd suggest to just submit this and figure out this issue separately
SG. but then probably we should not land broken tests?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
From googleclient/chrome/chromium_gwsq/ipc/config.gwsq:
IPC: cl...@chromium.org
📎 It looks like you’re making a possibly security-sensitive change! 📎 IPC security review isn’t a rubberstamp, so your friendly security reviewer will need a fair amount of context to review your CL effectively. Please review your CL description and code comments to make sure they provide context for someone unfamiliar with your project/area. Pay special attention to where data comes from and which processes it flows between (and their privilege levels). Feel free to point your security reviewer at design docs, bugs, or other links if you can’t reasonably make a self-contained CL description. (Also see https://cbea.ms/git-commit/).
IPC reviewer(s): cl...@chromium.org
Reviewer source(s):
cl...@chromium.org is from context(googleclient/chrome/chromium_gwsq/ipc/config.gwsq)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
});Can you add a .catch() block here so we can determine the error during debugging?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |