Skip to content

Highlight that the link to unsafe-escaping shows why it is unsafe. #4561

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jul 22, 2020
Merged

Highlight that the link to unsafe-escaping shows why it is unsafe. #4561

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion xml/System.Text.Encodings.Web/JavaScriptEncoder.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,7 +192,7 @@ Unlike the <xref:System.Text.Encodings.Web.JavaScriptEncoder.Default> encoding (

Unlike the <xref:System.Text.Encodings.Web.JavaScriptEncoder.Default> encoder, this encoder instance allows some other characters (such as '+') to go through unescaped and therefore must be used cautiously.

For more information, see [Serialize all characters](/dotnet/standard/serialization/system-text-json-how-to#serialize-all-characters).
For more information about why this could be **unsafe**, see [Serialize all characters](/dotnet/standard/serialization/system-text-json-how-to#serialize-all-characters).

]]></format>
</remarks>
Expand Down