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

[Suggestion] It would be better to open the webpage in a browser after executing command "Dapr: Report Issue" #224

Open
v-mengwe opened this issue Jan 12, 2022 · 1 comment
Labels
AT-CTI Issues found by internal test team enhancement Update to existing feature

Comments

@v-mengwe
Copy link

OS: All
Build Version: 20220111.3
Regression: Not a Regression

Repro Steps:

  1. F1 -> Dapr: Report Issue.
  2. Check whether opens the webpage.

Actual:
Open a window.
image

Suggestion:
It would be better to open the webpage in a browser.

@v-mengwe v-mengwe added the AT-CTI Issues found by internal test team label Jan 12, 2022
@philliphoff
Copy link
Member

The dialog is the standard VS Code error reporting dialog, used by VS Code and many of its extensions. The intent behind it (I assume) is to have a consistent means of reporting errors related to VS Code and 1st/3rd party extensions, automate the collection of certain information, and automate the creation of issues in GitHub.

That said, it looks like there is some common reporting-related functionality in the vscode-azureextensionui library that provides similar behavior, while also adding some niceties such as caching error notifications to make it easier to report them than copy/pasting. Our vscode-docker extension has switched over to this new functionality. We should consider doing the same for this extension.

@philliphoff philliphoff added the enhancement Update to existing feature label Jan 12, 2022
@philliphoff philliphoff added this to the Future milestone Jan 12, 2022
@philliphoff philliphoff removed this from the Future milestone Feb 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AT-CTI Issues found by internal test team enhancement Update to existing feature
Projects
None yet
Development

No branches or pull requests

2 participants