Skip to content

Conversation

@thaystg
Copy link
Member

@thaystg thaystg commented Nov 11, 2022

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.

@thaystg thaystg requested a review from radical as a code owner November 11, 2022 12:34
@ghost ghost added the area-Debugger-mono label Nov 11, 2022
@ghost ghost assigned thaystg Nov 11, 2022
@ghost
Copy link

ghost commented Nov 11, 2022

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

Backport of #78171 to release/7.0

/cc @thaystg

Customer Impact

Testing

Risk

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.

Author: thaystg
Assignees: thaystg
Labels:

area-Debugger-mono

Milestone: -

@thaystg thaystg requested a review from lewing November 11, 2022 12:34
@thaystg thaystg added the Servicing-consider Issue for next servicing release review label Nov 11, 2022
@thaystg
Copy link
Member Author

thaystg commented Nov 14, 2022

Please, do not merge.

@radical radical added the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Nov 14, 2022
@thaystg thaystg changed the title [release/7.0] [wasm][debugger] Don't need to escape special characters anymore [release/7.0] [wasm][debugger] Don't need to escape any letter or digit Nov 14, 2022
@radical radical removed the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Nov 14, 2022
Copy link
Member

@radical radical left a 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.

@thaystg thaystg changed the title [release/7.0] [wasm][debugger] Don't need to escape any letter or digit [release/7.0] [wasm][debugger] Don't escape accented letters Nov 14, 2022
@carlossanlop
Copy link
Contributor

This was approved by Tactics via email and is signed off by area owner. No OOB package authoring changes needed for this.
I'm just waiting for the CI to finish before merging.

@carlossanlop carlossanlop added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Nov 15, 2022
@carlossanlop
Copy link
Contributor

Failures happened all in the installer legs, none seem related to this change (it's all network/infra issues).

@carlossanlop carlossanlop merged commit c38b76a into dotnet:release/7.0 Nov 15, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Dec 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-Debugger-mono Servicing-approved Approved for servicing release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants