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.
This pull request improves the handling of ASCII characters in JSON and YAML editing workflows, ensuring that characters like
+,/, and#are not unnecessarily escaped. It also updates launch profiles for easier environment selection and bumps the project version to 1.0. The most important changes are grouped below:JSON and YAML encoding improvements:
StructuredEditHelper.BuildJsonContentto use a relaxed JSON encoder (JavaScriptEncoder.UnsafeRelaxedJsonEscaping), so ASCII characters such as+,/, and#are preserved in both property names and values, making the output more natural for plain-text editing. [1] [2]_StructuredEditHelper.csto verify that JSON and YAML editors correctly preserve ASCII characters in both property names and values, and that roundtripping edits does not alter these characters. [1] [2]Development tooling and configuration:
launchSettings.jsonto provide multiple profiles (Production,Slask, andChoose Enpoint), making it easier to select different AppConfig endpoints for local development and testing.Versioning:
version.jsonfrom0.2to1.0, indicating a major release milestone.