-
Notifications
You must be signed in to change notification settings - Fork 35.7k
add onTerminal activation event
#254444
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
add onTerminal activation event
#254444
Conversation
src/vs/workbench/services/extensions/common/extensionsRegistry.ts
Outdated
Show resolved
Hide resolved
Co-authored-by: Daniel Imms <2193314+Tyriar@users.noreply.github.com>
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.
Let's merge after we get the ok in the API sync.
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.
Verifica
| this._register(instance.onDidChangeShellType(() => this._extensionService.activateByEvent(`onTerminal:${instance.shellType}`))); | ||
| if (instance.shellType) { | ||
| this._extensionService.activateByEvent(`onTerminal:${instance.shellType}`); | ||
| } | ||
| return instance; |
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.
You can't register instance listeners against terminalservice like this as the references will remain when the terminal instance is disposed, potentially holding onto the TerminalInstance reference. You should do this in _initInstanceListeners
fix #252413