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

Use 'workbench.action.openIssueReporter' to report issues for the extension #2553

Closed
dgolovin opened this issue Oct 7, 2022 · 5 comments · Fixed by #2774
Closed

Use 'workbench.action.openIssueReporter' to report issues for the extension #2553

dgolovin opened this issue Oct 7, 2022 · 5 comments · Fixed by #2774
Assignees
Milestone

Comments

@dgolovin
Copy link
Collaborator

dgolovin commented Oct 7, 2022

Here is an example for Python extension.
https://github.com/microsoft/vscode-python/blob/ce62901d594bf222b3a3f827b5c8998d54ba901a/src/client/common/application/commands/reportIssueCommand.ts#L100

image

@mohitsuman mohitsuman added this to the 1.1.0 milestone Oct 10, 2022
@mohitsuman mohitsuman modified the milestones: 1.1.0, 1.2.0 Nov 23, 2022
@mohitsuman mohitsuman modified the milestones: 1.2.0, 1.3.0 Jan 4, 2023
@msivasubramaniaan
Copy link
Collaborator

@degolovi I need some clarification on this issue

  • Which link you clicked for the attached popup open?

  • Where we need the issue report on our extension?

  • Why we need it?

@dgolovin
Copy link
Collaborator Author

To open report window use
image

@dgolovin
Copy link
Collaborator Author

We already have it here

image

and as a navigation button in Application explorer

image

All this to get user feedback right from vscode window.

@rgrunber
Copy link
Member

I agree here. We should be using the platform's issue reporting API and pre-filling it with values that make it relevant for us. I think it's a little nicer than the current approach which just uses the bugs property in the package.json to generate a url and pass it to vscode.open command with a query string.

@msivasubramaniaan
Copy link
Collaborator

I agree here. We should be using the platform's issue reporting API and pre-filling it with values that make it relevant for us. I think it's a little nicer than the current approach which just uses the bugs property in the package.json to generate a url and pass it to vscode.open command with a query string.

@dgolovin and @rgrunber
Trying to achieve something here. Here attached the reference screen and the issue which created through workbench.action.openIssueReporter
image

Will try to customize the screen in terms of width and height and other items if possible. Also used issueReport.md for the body content. Let me know if anything needs to added on it as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
4 participants