-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
Report Issue for Remote extensions doesn't work #174404
Comments
Looks like @TylerLeonhardt might own this. vscode/src/vs/workbench/contrib/issue/electron-sandbox/issue.contribution.ts Lines 23 to 29 in 550fdeb
|
It was me all along 😱 I will change Web to be more like Desktop. |
I just debugged this and my issue reporter command is never fired. I think is an issue somewhere in this: vscode/src/vs/workbench/contrib/remote/browser/remote.ts Lines 317 to 370 in 7570fad
The repro steps:
nothing happens. |
To verify:
|
Sorry for the false alarm there @TylerLeonhardt ! |
@TylerLeonhardt where is this? |
I ran across this while trying to create report issue markdown links for notebooks. Clicking the report issue item in the help section of the remote explorer does nothing and I believe its because of improper arguments format for the report issue command here:
vscode/src/vs/workbench/contrib/remote/browser/remote.ts
Line 411 in bb920e8
The correct argument is an object with an extensionId property.
The text was updated successfully, but these errors were encountered: