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

debugWithChrome is weird #71176

Closed
jrieken opened this issue Mar 26, 2019 · 2 comments
Closed

debugWithChrome is weird #71176

jrieken opened this issue Mar 26, 2019 · 2 comments
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues

Comments

@jrieken
Copy link
Member

jrieken commented Mar 26, 2019

re #71074

I find it rather weird that vscode as a product suggests to configure something that requires an extension. Isn't the logical separation of concerns that the chrome-debug-extension contributes that configuration value?

Screenshot 2019-03-26 at 15 09 04

@weinand
Copy link
Contributor

weinand commented Mar 26, 2019

yes, fully agree.
/duplicate #69339

@vscodebot vscodebot bot added the *duplicate Issue identified as a duplicate of another issue(s) label Mar 26, 2019
@weinand weinand added debug Debug viewlet, configurations, breakpoints, adapter issues and removed *duplicate Issue identified as a duplicate of another issue(s) labels Mar 26, 2019
@vscodebot
Copy link

vscodebot bot commented Mar 26, 2019

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Mar 26, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators May 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues
Projects
None yet
Development

No branches or pull requests

2 participants