-
Notifications
You must be signed in to change notification settings - Fork 532
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only allow one window to run export per user #8123
base: export-integration
Are you sure you want to change the base?
Conversation
Export will continue in a different window if one was closed Close #8063 Co-authored-by: wrd <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job making it work! Distributed things are hard!
@@ -187,6 +199,7 @@ export class MailExportController { | |||
} catch (e) { | |||
if (isOfflineError(e)) { | |||
console.log(TAG, "Offline, will retry later") | |||
// FIXME: should we use scheduler here too? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there isn't a strong reason to, maybe only to make it testable
@@ -73,6 +73,7 @@ export class ApplicationWindow { | |||
private readonly localShortcut: LocalShortcutManager, | |||
private readonly themeFacade: DesktopThemeFacade, | |||
private readonly remoteBridge: RemoteBridge, | |||
private desktopExportLocks: Set<string>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
napkin pitch: what if we make the "window cleanup" mechanism more generic and inject some listener here instead? and coordination of these listeners can be outside of the poor ApplicationWindow
.
Export will continue in a different window if one was closed
Close #8063