-
Notifications
You must be signed in to change notification settings - Fork 29.5k
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
Provide a command to launch getting started for a particular extension #119725
Comments
Added a vscode.commands.executeCommand('workbench.action.openWalkthrough', 'jakearl.md-to-html#exampleProject', true); |
When I call either of these: // <extid>#<stepid>
commands.executeCommand('workbench.action.openWalkthrough', 'tyriar.luna-paint#luna.interfaceOverview', true);
// <extid>#<walkthroughid>
commands.executeCommand('workbench.action.openWalkthrough', 'tyriar.luna-paint#exampleProject', true); This is the result: Am I doing something wrong? Also should open to side only open to side when there is an existing editor in the first group? |
I was missing the capital T |
Actually I think this should be case insensitive just like |
Going to close this out for verification this milestone, opened #125414 to track case insensitivity |
Can anyone here help me with how to highlight a specific step/tile in a walkthrough? That does not seem to be documented but according to a quoted text it seems it should be possible:
|
When I adopt getting started in Luna Paint I'd like to tell the users that they can access the getting started guide/feature overview from within the tool by running some command. As such I'd like to be able to run some command with an arg being my extension ID to open it directly. That way I could wrap it in my own command.
Perhaps this should open to the side by default?
The text was updated successfully, but these errors were encountered: