update llms.txt file for System.Text.Json#52302
Draft
kartheekp-ms wants to merge 7 commits intollmstxtfrom
Draft
update llms.txt file for System.Text.Json#52302kartheekp-ms wants to merge 7 commits intollmstxtfrom
kartheekp-ms wants to merge 7 commits intollmstxtfrom
Conversation
Added detailed information about new features in .NET 10 related to System.Text.Json, best practices in llms.txt file
Removed detailed sections about `JsonSerializerOptions.Strict`, `AllowDuplicateProperties`, `PipeReader` support, and `ReferenceHandler` from the documentation and added a link to the official doc.
Added new APIs and features introduced in .NET 10 for JSON serialization, including best-practice presets and options for handling duplicate properties.
aortiz-msft
requested changes
Mar 16, 2026
| - **Prefer `Strict` for new projects.** The `Strict` preset catches common mistakes (unmapped members, duplicate keys, null violations) at deserialization time rather than silently ignoring them. | ||
| - **Serialize to UTF-8 when possible.** `SerializeToUtf8Bytes()` is 5–10% faster than string-based serialization because it avoids UTF-16 conversion. | ||
|
|
||
| ## Topics |
There was a problem hiding this comment.
Do we need all these topics? Would removing all of these reduce token usage for the corresponding evaluation while maintaining accuracy and perf improvements? If not, what's the minimal set?
Contributor
Author
There was a problem hiding this comment.
It is hard to finalize list of topics without evaluating how Copilot handles related tasks with and without these topics. Maybe we can use learn.microsoft.com metrics and add links to frequently visited topics.
Contributor
Author
There was a problem hiding this comment.
As discussed, I have removed topics from the file.
Added new APIs and breaking changes for .NET 10 serialization.
Updated the description of property name conflict validation to suggest renaming conflicting properties.
Reinstate the note about serializing to UTF-8 for performance benefits.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.