Skip to content
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 reset the completed steps of a walkthrough #212819

Open
BenjaminScholtens opened this issue May 15, 2024 · 2 comments
Open
Assignees
Labels
feature-request Request for new features or functionality
Milestone

Comments

@BenjaminScholtens
Copy link

Currently, VSCode allows users to reset all walkthroughs using the command workbench.action.resetGettingStartedProgress. However, there is no means to execute a command from an extension to reset a specific walkthrough.

Feature Request:

Please provide a command that allows resetting the completed steps of a specific walkthrough. This would enable extensions to programmatically reset the progress of a particular walkthrough, enhancing the user experience by providing more granular control over walkthrough progress.

Proposed Implementation:

Introduce a new command, such as workbench.action.resetSpecificWalkthroughProgress, which can be executed with the necessary parameters to reset a specific walkthrough.

Example Usage:

vscode.commands.executeCommand(
  "workbench.action.resetSpecificWalkthroughProgress",
  "extensionPublisher.extensionName.#WalkThroughId"
);

Use Case:

This feature would be particularly useful for extension developers who wish to provide users with the ability to restart specific walkthroughs without affecting the progress of other walkthroughs. It would also be beneficial in scenarios where a walkthrough needs to be revisited or reset due to updates or changes in the extension.

Thank you for considering this feature request.

@bhavyaus bhavyaus added the feature-request Request for new features or functionality label May 28, 2024
@bhavyaus bhavyaus added this to the Backlog Candidates milestone May 28, 2024
@VSCodeTriageBot
Copy link
Collaborator

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

@VSCodeTriageBot
Copy link
Collaborator

🙂 This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

3 participants