-
Notifications
You must be signed in to change notification settings - Fork 196
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
Enhance support for configuring debuggers used for Blazor WASM apps #2774
Conversation
src/Razor/src/Microsoft.AspNetCore.Razor.VSCode.Extension/package.json
Outdated
Show resolved
Hide resolved
}, | ||
"browserConfig": { | ||
"description": "Options based", | ||
"type": "object" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it just an object because it's a generic key=>value dictionary with no structure?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does have a structure. It should only contain the properties that you would pass to the JS debugger (or .NET debugger in the case above). I'll add docs to clarify this.
We could copy/paste the entire config setup for the .NET/JS debuggers here but that didn't seem sustainable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like you'll probably get some push back on this only because users will be "off on their own" to setup these configuration options. VSCode users typically rely heavily on IntelliSense to configure things like this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmmmm. Good point. I'll strike a balance by including the options that users are more likely to use here.
...or/src/Microsoft.AspNetCore.Razor.VSCode/src/BlazorDebug/BlazorDebugConfigurationProvider.ts
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM though my area knowledge is weak here.
...or/src/Microsoft.AspNetCore.Razor.VSCode/src/BlazorDebug/BlazorDebugConfigurationProvider.ts
Show resolved
Hide resolved
@@ -114,6 +89,7 @@ export class BlazorDebugConfigurationProvider implements vscode.DebugConfigurati | |||
inspectUri: '{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}', | |||
trace: configuration.trace || false, | |||
noDebug: configuration.noDebug || false, | |||
...configuration.browserConfig, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need a separate category of #PranavPoints for Typescript?
Summary of the changes
Fixes: dotnet/aspnetcore#27518, dotnet/vscode-csharp#4161, dotnet/vscode-csharp#4108