Skip to content
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.

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

[JsonSerializer] Add support for out-of-order metadata reads. #97474

Merged

Conversation

eiriktsarpalis
Copy link
Member

Makes the following changes:

  1. Adds support for out-of-order metadata reads in JsonSerializer.
  2. Ensures that read JSON property names are always unescaped.

Fix #72604.

Copy link

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

@ghost ghost assigned eiriktsarpalis Jan 24, 2024
@ghost
Copy link

ghost commented Jan 24, 2024

Tagging subscribers to this area: @dotnet/area-system-text-json, @gregsdennis
See info in area-owners.md if you want to be subscribed.

Issue Details

Makes the following changes:

  1. Adds support for out-of-order metadata reads in JsonSerializer.
  2. Ensures that read JSON property names are always unescaped.

Fix #72604.

Author: eiriktsarpalis
Assignees: -
Labels:

area-System.Text.Json, new-api-needs-documentation

Milestone: -

@eiriktsarpalis eiriktsarpalis added this to the 9.0.0 milestone Jan 24, 2024
@eiriktsarpalis eiriktsarpalis added the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Jan 24, 2024
@eiriktsarpalis
Copy link
Member Author

New API pending approval, please do not merge yet.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

JsonSerializer: Allow out-of-order reading of metadata properties.
4 participants