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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal TerminalExitStatus.reason #152833
Conversation
*/ | ||
dispose(immediate?: boolean): void; |
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.
Is immediate
deprecated? There was only one place that used it (in terminalQuickAccess.ts
) but I changed it to terminalService.safeDisposeTerminal
so it's the same as other calls.
If not I'll revet this change.
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.
I'm not totally sure what the current state of this is, but it was always a bit of a hack to add a param to dispose like this so I'd want to move away from it if we were to change things in this area.
@Tyriar Does proposed change make sense to you? We would really appreciate such API like stable though to unblock our customers. 馃檹 |
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.
The idea seems reasonable, I'll make a note to bring this to the next API sync which will be in 2 weeks.
*/ | ||
dispose(immediate?: boolean): void; |
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.
I'm not totally sure what the current state of this is, but it was always a bit of a hack to add a param to dispose like this so I'd want to move away from it if we were to change things in this area.
c34b852
to
4e102e6
Compare
@Tyriar thank you! Is API sync internal or we can follow it somehow as well? |
@akosyakov it is internal and we will post a summary after that happens |
Discussed at the API sync and we think the shape looks good. Just the one question above |
Co-authored-by: Daniel Imms <2193314+Tyriar@users.noreply.github.com>
I forgot to ask this, how long does it take for a proposal API to become stable? I just realized that even if this is merged we won't be able to use it in our extension and publish it to the marketplace 馃槄 |
It needs to stay proposed for at least a month, this one's not complex so 1 month seems right |
@Tyriar @meganrogge Thank you a lot 馃檹 Is it good to land? I believe @jeanp413 addressed the feedback. |
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.
Looks good, will merge after a full test pass
This PR fixes #130231
Implements API proposal
TerminalExitStatus.reason
to address issue #130231Added
Shutdown
(main motivation for #130231) andUnknown
(i.e. any other reasons) reasonsSide note, after working on this, I would say that firing
vscode.window.onDidCloseTerminal
on shutdown is more of a bug than a feature, if some extension terminal logic is required to execute on shutdown then usingcontext.subscriptions
would be preferred I think but changingonDidCloseTerminal
behavior would be a breaking change 馃cc @Tyriar