-
Notifications
You must be signed in to change notification settings - Fork 29k
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
Adopt registerWorkbenchContribution2 for welcome page #204440
Conversation
@bhavyaus thanks! This should be good to go: the editor resolver code still needs to run very early to register the editor. Only the |
ff3f265
to
a64bdce
Compare
f98251c
to
398c095
Compare
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 do not understand the revert of the changes.
Sorry, had forgotten to push.
@bhavyaus with my commit, it should work. the editor resolver needs to be there on startup for the editor to actually load. |
Also fixes: #193623
There are two scenarios to consider here for the GettingStartedInput editor type:
The startup editor (welcome page) is opened automatically if workbench.startupEditor setting is enabled by the user or on first launch for new users.
OpenWalkthrough command is invoked on Activation as described by the user here
onStartupFinished
activation event has no criteria for startup finishing #193623StartupPageRunnerContribution
withWorkbenchPhase.AfterRestored
supports Scenario 1StartupPageEditorResolverContribution
withWorkbenchPhase.BlockRestore
supports Scenario 2 by ensuring the editorResolver has time to register the input type.