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

Allow extensions to contribute to issue body when using Issue Reporter #148675

Closed
karrtikr opened this issue May 3, 2022 · 4 comments
Closed
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality issue-reporter Issue reporter widget issues
Milestone

Comments

@karrtikr
Copy link
Contributor

karrtikr commented May 3, 2022

When an extension, say Python, is selected in the report issue dropdown:

"Steps to reproduce" should be auto-filled with extension specific templates if available.

Right now the workaround is that every extension has its own report issue command, which isn't always used when reporting issues (users rely on the general Help: Report Issue instead):

@TylerLeonhardt
Copy link
Member

related: #46726

@TylerLeonhardt TylerLeonhardt added issue-reporter Issue reporter widget issues feature-request Request for new features or functionality labels May 4, 2022
@TylerLeonhardt TylerLeonhardt added this to the Backlog milestone May 4, 2022
@karrtikr
Copy link
Contributor Author

karrtikr commented May 4, 2022

An easy solution for this would be to provide a hook when an extension is selected in the dropdown, which then launches the extension specific report command. This can be specified in 'package.json'.

@bwateratmsft
Copy link
Contributor

For Docker and several Azure extensions, we'd like to use the built-in issue reporter but also attach some additional data (error details, call stack, etc.), while still requiring users to fill something into the repro steps field.

@TylerLeonhardt
Copy link
Member

/duplicate #46726

@vscodenpa vscodenpa added the *duplicate Issue identified as a duplicate of another issue(s) label Dec 8, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Jan 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality issue-reporter Issue reporter widget issues
Projects
None yet
Development

No branches or pull requests

4 participants