Should Utf8JsonReader expose whether a JSON string needs to be unescaped or not?

[ahsonkhan]

The Utf8JsonReader already knows whether a particular JSON string needs to be unescaped. If it stored that fact (and publicly exposed it), users like JsonDocument would not need to duplicate that check (which means we save the search for a backslash in the json payload).

https://github.com/dotnet/corefx/blob/77096755443730962810662501f82550fdb4656d/src/System.Text.Json/src/System/Text/Json/Utf8JsonReader.cs#L760-L771

cc @bartonjs

[ahsonkhan]

Adding an internal field for JsonDocument to leverage does not require a public API change and should be done as an implementation detail similar to us storing 'e' when processing numbers: dotnet/corefx#34386. For that component (at least), marking as up-for-grabs.

[ahsonkhan]

Adding an internal field for JsonDocument to leverage does not require a public API change and should be done as an implementation detail similar to us storing 'e' when processing numbers: dotnet/corefx#34386. For that component (at least), marking as up-for-grabs.

This was completed as part of dotnet/corefx#34485

[ghost]

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of the experimental issue cleanup initiative we are currently trialing in a limited number of areas. Please share any feedback you might have in the linked issue.

[ghost]

This issue will now be closed since it had been marked no recent activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

[ahsonkhan]

There is a related issue, which acts as a follow-up to this one: #45167