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

Document System.Text.Json serialization property ordering #25599

Closed
Tracked by #24212
tdykstra opened this issue Aug 11, 2021 · 0 comments · Fixed by #25777
Closed
Tracked by #24212

Document System.Text.Json serialization property ordering #25599

tdykstra opened this issue Aug 11, 2021 · 0 comments · Fixed by #25777
Assignees
Labels
doc-enhancement Improve the current content [org][type][category] dotnet-fundamentals/svc Pri1 High priority, do before Pri2 and Pri3

Comments

@tdykstra
Copy link
Contributor

https://devblogs.microsoft.com/dotnet/announcing-net-6-preview-7/#libraries-system-text-json-serialization-property-ordering


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label Aug 11, 2021
@PRMerger20 PRMerger20 added dotnet-fundamentals/svc Pri1 High priority, do before Pri2 and Pri3 labels Aug 11, 2021
@tdykstra tdykstra self-assigned this Aug 11, 2021
@tdykstra tdykstra added the doc-idea Indicates issues that are suggestions for new topics [org][type][category] label Aug 11, 2021
@dotnet-bot dotnet-bot removed the ⌚ Not Triaged Not triaged label Aug 11, 2021
@tdykstra tdykstra added doc-enhancement Improve the current content [org][type][category] and removed doc-idea Indicates issues that are suggestions for new topics [org][type][category] labels Aug 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-enhancement Improve the current content [org][type][category] dotnet-fundamentals/svc Pri1 High priority, do before Pri2 and Pri3
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants