[release/13.1] Escape backslashes in path string to discovered vite config #13822
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dotnet-policy-service
bot
added
Re-opened Github-Action PR
and removed
Closed Github-Action PR
labels
Contributor
Author
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 13822Or
iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 13822" |
danegsta
approved these changes
Jan 9, 2026
davidfowl
approved these changes
Jan 13, 2026
Member
davidfowl
left a comment
davidfowl
left a comment
There was a problem hiding this comment.
LGTM - simple backslash escape fix for Vite config paths.
This was referenced Feb 11, 2026
Closed
This was referenced Feb 12, 2026
Open
Open
Open
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #13814 to release/13.1
/cc @danegsta
Customer Impact
A path string in a log message for Vite HTTPS support wasn’t being properly escaped leading to errors if a path segment starts with certain characters.
Testing
Manually verified the string is escaped correctly with the change.
Risk
Low
Regression?
No