Commit-Queue | +1 |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
abstract installSoda(): void;
nit: add comment for the expected way to handle errors.
let dispose: Dispose|null = null;
Do we want to set `dispose` to null after calling it...? What will happen if we call dispose() twice?
// Don't enable SODA if it's unavailable. All UI to enable transcription
// are gated behind transcriptionAvailable.
Hmm if it's gated by UI already, do we still need the `&&` below?
console.log('SODA installation requested');
Do we want to keep this console.log()?
Maybe we should have our own logger that will send event logs alone with the feedback report :P
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
nit: add comment for the expected way to handle errors.
Done
Do we want to set `dispose` to null after calling it...? What will happen if we call dispose() twice?
We wouldn't ever call dispose twice here since it's called in an effect block, and that got cancelled when dispose is called the first time. The second call to dispose is a no-op anyway.
The code is structued in this way due to the limitation that the effect callback is called synchronously on the first call, so the dispose won't be set at that time... Hmm so there's a bug here that the first call won't be able to stop the effect :P
Changed the effect interface to have a disposed function passed in to be used inside the effect callback.
// Don't enable SODA if it's unavailable. All UI to enable transcription
// are gated behind transcriptionAvailable.
Hmm if it's gated by UI already, do we still need the `&&` below?
We still need this one since this one in particular is called in connectedCallback and not gated by UI.
Do we want to keep this console.log()?
Maybe we should have our own logger that will send event logs alone with the feedback report :P
This is for dev so we want to log to console for easier debugging.
(Note that we have eslint that disallow console.log for places other than dev)
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. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
From googleclient/chrome/chromium_gwsq/ipc/config.gwsq:
IPC: toyo...@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): toyo...@chromium.org
Reviewer source(s):
toyo...@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. |
Auto-Submit | +1 |
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. |