- 
                Notifications
    You must be signed in to change notification settings 
- Fork 5.2k
[release/7.0] [wasm][debugger] Don't escape accented letters #78217
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
[release/7.0] [wasm][debugger] Don't escape accented letters #78217
Conversation
| Tagging subscribers to this area: @thaystg Issue DetailsBackport of #78171 to release/7.0 /cc @thaystg Customer ImpactTestingRiskIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed. 
 | 
| Please, do not merge. | 
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.
Changes look fine for 7.0 branch. @thaystg will explore using Uri.EscapeDataString, and friends to handle the escaping in follow up PRs.
| This was approved by Tactics via email and is signed off by area owner. No OOB package authoring changes needed for this. | 
| Failures happened all in the installer legs, none seem related to this change (it's all network/infra issues). | 
Backport of #78171 to release/7.0
/cc @thaystg
Customer Impact
When the customer adds a breakpoint in a file that contains any special character like (swedish characters) and the breakpoint is hit, the file is not opened correctly on VS.
Testing
Manually tested using a Blazor app, adding special characters in the folder, in the project name and in the source file name.
Risk
Low risk, do not escape all the letters and not only the ones unaccented.
IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.