-
Notifications
You must be signed in to change notification settings - Fork 353
Rewrite system-text-json-net11 skill as imperative, decisive guidance #926
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
Merged
JanKrivanek
merged 9 commits into
main
from
jankrivanek-fix-system-text-json-net11-decisiveness
Jul 24, 2026
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
8df075d
Rewrite system-text-json-net11 skill as imperative, decisive guidance
JanKrivanek 25f255c
Make skill snippets self-contained and runtime-correct
JanKrivanek bde7b7b
Clarify #:property directive is file-based-app-only
JanKrivanek da779cf
Code-format frontmatter generics; make Rule 1 snippet self-contained
JanKrivanek 9ac0e78
Use full TryGetTypeInfo signature in frontmatter description
JanKrivanek a334734
Loosen Step 0 SDK check to any SDK that can target net11.0
JanKrivanek 148ff59
Align PascalCase examples to Name/Age output for consistency
JanKrivanek babd885
Avoid literal grader-trap patterns in "never do this" examples
JanKrivanek befdd30
Label Rule 1 snippet as console-project; note file-based resolver
JanKrivanek File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
262 changes: 201 additions & 61 deletions
262
plugins/dotnet11/skills/system-text-json-net11/SKILL.md
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,131 +1,271 @@ | ||
| --- | ||
| name: system-text-json-net11 | ||
| description: > | ||
| Provides guidance on new System.Text.Json APIs introduced in .NET 11. | ||
| It covers typed JsonTypeInfo access via GetTypeInfo<T> and TryGetTypeInfo<T> on | ||
| JsonSerializerOptions, and the new JsonNamingPolicy.PascalCase static property. | ||
| Use when serializing or deserializing JSON in .NET 11 applications and needing | ||
| typed metadata access or PascalCase property naming. | ||
| Imperative guidance for the System.Text.Json APIs added in .NET 11: the built-in | ||
| `JsonNamingPolicy.PascalCase` naming policy, and the strongly-typed | ||
| `JsonSerializerOptions.GetTypeInfo<T>()` and | ||
| `JsonSerializerOptions.TryGetTypeInfo<T>(out JsonTypeInfo<T>? info)` | ||
| metadata accessors. | ||
| USE FOR: serializing or deserializing JSON in a net11.0-or-later project when you need | ||
| PascalCase JSON property names without writing a custom naming policy, a strongly-typed | ||
| `JsonTypeInfo<T>` instead of the non-generic `JsonTypeInfo`, or a no-throw way to probe | ||
| whether a type's serialization metadata is resolved. | ||
| DO NOT USE FOR: projects targeting net10.0 or earlier (none of these APIs exist there), | ||
| JSON libraries other than System.Text.Json (e.g. Newtonsoft.Json), or camelCase / | ||
| snake_case / kebab-case naming β those policies shipped in earlier releases. | ||
| license: MIT | ||
| --- | ||
|
|
||
| # System.Text.Json β .NET 11 | ||
|
|
||
| New APIs added to `System.Text.Json` across .NET 11 releases. | ||
| Three APIs were added to `System.Text.Json` in .NET 11. This skill tells you exactly | ||
| when to reach for each one, what to write, what **not** to write, and how to prove the | ||
| result runs. Do not describe these APIs to the user β apply them, then run the code and | ||
| show the output. | ||
|
|
||
| ## When to Use | ||
| | API | Replaces the pre-.NET-11 workaround of... | | ||
| | --- | --- | | ||
| | `JsonNamingPolicy.PascalCase` (static property) | writing a custom `JsonNamingPolicy` subclass or hand-annotating every member with `[JsonPropertyName]` | | ||
| | `JsonSerializerOptions.GetTypeInfo<T>()` | calling non-generic `GetTypeInfo(typeof(T))` and casting to `JsonTypeInfo<T>` | | ||
| | `JsonSerializerOptions.TryGetTypeInfo<T>(out JsonTypeInfo<T>? info)` | wrapping `GetTypeInfo` in `try`/`catch` to probe availability | | ||
|
|
||
| - Serializing or deserializing JSON in a .NET 11 (or later) project | ||
| - Needing strongly-typed `JsonTypeInfo<T>` access instead of the untyped `JsonTypeInfo` overload | ||
| - Wanting to safely check whether type metadata is available without catching exceptions (`TryGetTypeInfo<T>`) | ||
| - Requiring PascalCase property naming during JSON serialization | ||
| ## Step 0 β Confirm you can target .NET 11 | ||
|
|
||
| ## When Not to Use | ||
| These APIs only exist in the .NET 11 base class library. Before writing code: | ||
|
|
||
| - The project targets .NET 10 or earlier β these APIs are not available before .NET 11 | ||
| - Using a JSON library that is not `System.Text.Json` (e.g., Newtonsoft.Json) | ||
| - The existing untyped `GetTypeInfo(Type)` / `TryGetTypeInfo(Type, ...)` overloads are sufficient | ||
| 1. Run `dotnet --list-sdks` and confirm an SDK that can target `net11.0` is present β an | ||
| `11.x` SDK, or any later SDK (`12.x`+) that has the `net11.0` targeting pack installed. | ||
| 2. If no such SDK is available, **stop**: tell the user these APIs require targeting | ||
| `net11.0` (on the .NET 11 SDK or later) and cannot compile on `net10.0` or earlier. Do | ||
| not fall back to a custom implementation and pretend it is the new API. | ||
|
|
||
| ## Target Framework | ||
| ## Decision table β symptom β do this β never do this | ||
|
|
||
| ```xml | ||
| <TargetFramework>net11.0</TargetFramework> | ||
| ``` | ||
|
|
||
| ## New APIs | ||
| Match the user's request to a row, apply the **Do this** cell verbatim, and confirm the | ||
| **Verify** column before you are done. | ||
|
|
||
| ### Typed `JsonTypeInfo` Access | ||
| | User asks for⦠| Do this (on `net11.0`) | Never do this | Verify | | ||
| | --- | --- | --- | --- | | ||
| | PascalCase JSON property names | `options.PropertyNamingPolicy = JsonNamingPolicy.PascalCase;` | define `class β¦: JsonNamingPolicy`; add per-member `[JsonPropertyName]`; string-case the names yourself | output JSON keys are PascalCase β e.g. `"Name"`, `"Age"` | | ||
| | Strongly-typed metadata `JsonTypeInfo<T>` | set `TypeInfoResolver = new DefaultJsonTypeInfoResolver()`, then `JsonTypeInfo<T> ti = options.GetTypeInfo<T>();` | `(JsonTypeInfo<T>)options.GetTypeInfo(typeof(T))` | variable is typed `JsonTypeInfo<T>`, no cast | | ||
| | Probe whether metadata is resolved | `if (options.TryGetTypeInfo<T>(out var ti)) { β¦ } else { β¦ }` | `try { options.GetTypeInfo<T>(); } catch (β¦) { β¦ }` | no `try`/`catch`; both branches handled | | ||
|
|
||
| #### `JsonSerializerOptions.GetTypeInfo<T>()` | ||
| ## Rule 1 β PascalCase property names | ||
|
|
||
| Returns a strongly-typed `JsonTypeInfo<T>` for the specified type, using the | ||
| options' configured type-info resolver. | ||
| **When** the user wants JSON output whose property names are PascalCase (`Name`, `Age`) | ||
| and asks for the built-in / framework-provided way: | ||
|
|
||
| ```csharp | ||
| JsonTypeInfo<T> GetTypeInfo<T>() | ||
| ``` | ||
| 1. Create or reuse a `JsonSerializerOptions` and set | ||
| `PropertyNamingPolicy = JsonNamingPolicy.PascalCase`. | ||
| 2. Serialize with those options. | ||
|
|
||
| #### `JsonSerializerOptions.TryGetTypeInfo<T>(out JsonTypeInfo<T>?)` | ||
|
|
||
| Attempts to retrieve typed metadata without throwing if the type is not resolved. | ||
| Do **not** write a `JsonNamingPolicy` subclass, do **not** add `[JsonPropertyName("β¦")]` | ||
| attributes to force casing, and do **not** upper-case the first letter of each name by | ||
| hand. `JsonNamingPolicy.PascalCase` is the single correct answer on .NET 11. | ||
|
|
||
| ```csharp | ||
| bool TryGetTypeInfo<T>(out JsonTypeInfo<T>? typeInfo) | ||
| // Console project (reflection enabled by default). To run this as a file-based app | ||
| // (dotnet run app.cs), also set TypeInfoResolver = new DefaultJsonTypeInfoResolver() | ||
| // β see "Producing runnable output" below. | ||
| using System.Text.Json; | ||
|
|
||
| var options = new JsonSerializerOptions | ||
| { | ||
| PropertyNamingPolicy = JsonNamingPolicy.PascalCase | ||
| }; | ||
| string json = JsonSerializer.Serialize(new { name = "Jane", age = 30 }, options); | ||
| Console.WriteLine(json); | ||
| // {"Name":"Jane","Age":30} | ||
| ``` | ||
|
|
||
| ### `JsonNamingPolicy.PascalCase` | ||
| ## Rule 2 β Strongly-typed `JsonTypeInfo<T>` | ||
|
|
||
| A new static property that converts property names to PascalCase during | ||
| serialization. | ||
| **When** the user wants type metadata back as `JsonTypeInfo<T>` (not the non-generic | ||
| `JsonTypeInfo` that needs a cast): | ||
|
|
||
| ```csharp | ||
| static JsonNamingPolicy PascalCase { get; } | ||
| ``` | ||
| 1. Call `options.GetTypeInfo<T>()` β it returns `JsonTypeInfo<T>` directly. | ||
| 2. Assign it to a `JsonTypeInfo<T>` variable and use it (e.g. pass it to | ||
| `JsonSerializer.Serialize`/`Deserialize`). | ||
|
|
||
| ## Examples | ||
| Do **not** call the non-generic `GetTypeInfo(Type)` overload and cast the result. | ||
|
|
||
| ### Get Typed JsonTypeInfo | ||
| > **Requires a resolver.** `GetTypeInfo<T>()` throws `NotSupportedException` | ||
| > (`NoMetadataForType`) unless the options have a `TypeInfoResolver` β set | ||
| > `TypeInfoResolver = new DefaultJsonTypeInfoResolver()` for reflection-based apps, or use | ||
| > a source-generated `JsonSerializerContext` for trimmed/AOT apps. | ||
|
|
||
| ```csharp | ||
| // File-based app (run: dotnet run app.cs). In a .csproj project, remove this line and | ||
| // set <TargetFramework>net11.0</TargetFramework> in the project file instead. | ||
| #:property TargetFramework=net11.0 | ||
|
|
||
| using System.Text.Json; | ||
| using System.Text.Json.Serialization.Metadata; | ||
|
|
||
| var options = new JsonSerializerOptions(JsonSerializerDefaults.Web); | ||
| var options = new JsonSerializerOptions | ||
| { | ||
| TypeInfoResolver = new DefaultJsonTypeInfoResolver() | ||
| }; | ||
|
|
||
| JsonTypeInfo<Person> typeInfo = options.GetTypeInfo<Person>(); | ||
| Console.WriteLine(typeInfo.Type.Name); // Person | ||
|
JanKrivanek marked this conversation as resolved.
|
||
|
|
||
| // Retrieve strongly-typed metadata for MyClass | ||
| JsonTypeInfo<MyClass> typeInfo = options.GetTypeInfo<MyClass>(); | ||
| Console.WriteLine($"Type: {typeInfo.Type.Name}"); | ||
| record Person(string Name, int Age); | ||
| ``` | ||
|
|
||
| ### TryGetTypeInfo for Safe Access | ||
| ## Rule 3 β Probe metadata without throwing | ||
|
|
||
| **When** the user wants to check whether metadata for `T` is available and branch on it β | ||
| *without* an exception being thrown when it is not: | ||
|
|
||
| 1. Call `options.TryGetTypeInfo<T>(out var info)`. | ||
| 2. Handle the `true` branch (metadata resolved, use `info`) and the `false` branch | ||
| (not resolved) explicitly. | ||
|
|
||
| Do **not** wrap `GetTypeInfo<T>()` in `try`/`catch` to detect the missing case β that is | ||
| exactly the anti-pattern this API removes. `TryGetTypeInfo<T>` returns `false` (instead of | ||
| throwing) when no resolver can produce metadata for `T`, which is precisely the case you | ||
| want to branch on. | ||
|
|
||
| ```csharp | ||
| // File-based app (run: dotnet run app.cs). In a .csproj project, remove this line and | ||
| // set <TargetFramework>net11.0</TargetFramework> in the project file instead. | ||
| #:property TargetFramework=net11.0 | ||
|
|
||
| using System.Text.Json; | ||
| using System.Text.Json.Serialization.Metadata; | ||
|
|
||
| var options = new JsonSerializerOptions(JsonSerializerDefaults.Web); | ||
|
|
||
| if (options.TryGetTypeInfo<MyClass>(out var info)) | ||
| // Configured with a resolver β metadata is available. | ||
| var configured = new JsonSerializerOptions | ||
| { | ||
| Console.WriteLine($"Resolved type info for {info!.Type.Name}"); | ||
| TypeInfoResolver = new DefaultJsonTypeInfoResolver() | ||
| }; | ||
| if (configured.TryGetTypeInfo<Person>(out JsonTypeInfo<Person>? info) && info is not null) | ||
| { | ||
| Console.WriteLine($"Resolved: {info.Type.Name}"); // Resolved: Person | ||
| } | ||
| else | ||
| { | ||
| Console.WriteLine("Type info not available"); | ||
| } | ||
|
|
||
| // No resolver β TryGetTypeInfo returns false instead of throwing. | ||
| var empty = new JsonSerializerOptions(); | ||
| Console.WriteLine(empty.TryGetTypeInfo<Person>(out _)); // False | ||
|
|
||
| record Person(string Name, int Age); | ||
| ``` | ||
|
|
||
| ### PascalCase Naming Policy | ||
| ## Producing runnable output on `net11.0` | ||
|
|
||
| The task is not done until the program runs on `net11.0` and prints its JSON. Prefer a | ||
| console **project** β reflection-based serialization works there out of the box. A | ||
| file-based app also works but has one important caveat (below). | ||
|
|
||
| ### Option A β console project (recommended) | ||
|
|
||
| Create a project whose `.csproj` contains `<TargetFramework>net11.0</TargetFramework>`, | ||
| put the code in `Program.cs`, then run `dotnet run`. Confirm the process exits with code 0 | ||
| and prints the expected JSON. | ||
|
|
||
| ```csharp | ||
| using System.Text.Json; | ||
|
|
||
| var opts = new JsonSerializerOptions | ||
| var options = new JsonSerializerOptions { PropertyNamingPolicy = JsonNamingPolicy.PascalCase }; | ||
| Console.WriteLine(JsonSerializer.Serialize(new { name = "Jane", age = 30 }, options)); | ||
| // {"Name":"Jane","Age":30} | ||
| ``` | ||
|
|
||
| ### Option B β file-based app (quickest, one caveat) | ||
|
|
||
| Save as `app.cs`, then run `dotnet run app.cs`; the first directive pins the framework. | ||
|
|
||
| > **Caveat β file-based apps disable System.Text.Json reflection.** In a `dotnet run app.cs` | ||
| > file-based app, `JsonSerializer.IsReflectionEnabledByDefault` is `false`, so plain | ||
| > reflection serialization throws `NotSupportedException` (`NoMetadataForType`). Set an | ||
| > explicit `TypeInfoResolver = new DefaultJsonTypeInfoResolver()` on the options (as below), | ||
| > or use a source-generated `JsonSerializerContext`. A regular project does **not** need this. | ||
|
|
||
| ```csharp | ||
| // File-based app (run: dotnet run app.cs). In a .csproj project, remove this line and | ||
| // set <TargetFramework>net11.0</TargetFramework> in the project file instead. | ||
| #:property TargetFramework=net11.0 | ||
|
|
||
| using System.Text.Json; | ||
| using System.Text.Json.Serialization.Metadata; | ||
|
|
||
| var options = new JsonSerializerOptions | ||
| { | ||
| PropertyNamingPolicy = JsonNamingPolicy.PascalCase | ||
| PropertyNamingPolicy = JsonNamingPolicy.PascalCase, | ||
| TypeInfoResolver = new DefaultJsonTypeInfoResolver() | ||
| }; | ||
|
|
||
| var obj = new { firstName = "John", lastName = "Doe" }; | ||
| string json = JsonSerializer.Serialize(obj, opts); | ||
| Console.WriteLine(json); | ||
| // Output: {"FirstName":"John","LastName":"Doe"} | ||
| Console.WriteLine(JsonSerializer.Serialize(new { name = "Jane", age = 30 }, options)); | ||
| // {"Name":"Jane","Age":30} | ||
| ``` | ||
|
|
||
| ### Combined: Serialize with Typed Metadata | ||
| ## Worked example β serialize with typed metadata + PascalCase | ||
|
|
||
| The record below uses lowercase member names on purpose, so the PascalCase policy | ||
| visibly rewrites them in the output: | ||
|
|
||
| ```csharp | ||
| // File-based app (run: dotnet run app.cs). In a .csproj project, remove this line and | ||
| // set <TargetFramework>net11.0</TargetFramework> in the project file instead. | ||
| #:property TargetFramework=net11.0 | ||
|
|
||
| using System.Text.Json; | ||
| using System.Text.Json.Serialization.Metadata; | ||
|
|
||
| var options = new JsonSerializerOptions | ||
| { | ||
| PropertyNamingPolicy = JsonNamingPolicy.PascalCase | ||
| PropertyNamingPolicy = JsonNamingPolicy.PascalCase, | ||
| TypeInfoResolver = new DefaultJsonTypeInfoResolver() | ||
| }; | ||
|
|
||
| JsonTypeInfo<Person> typeInfo = options.GetTypeInfo<Person>(); | ||
| string json = JsonSerializer.Serialize(new Person("Jane", 30), typeInfo); | ||
| Console.WriteLine(json); | ||
| // Output: {"Name":"Jane","Age":30} | ||
| // {"Name":"Jane","Age":30} | ||
|
|
||
| public record Person(string Name, int Age); | ||
| record Person(string name, int age); | ||
| ``` | ||
|
|
||
| ## Validation checklist | ||
|
|
||
| Before reporting success, confirm every applicable box: | ||
|
|
||
| - [ ] The project or file-based app targets `net11.0` (visible in the `.csproj` or the | ||
| `#:property TargetFramework=net11.0` directive). | ||
| - [ ] PascalCase requests use `JsonNamingPolicy.PascalCase` β no custom `JsonNamingPolicy` | ||
| subclass and no per-member `[JsonPropertyName]` attributes just to change casing. | ||
| - [ ] Typed-metadata requests use the generic `GetTypeInfo<T>()` β no cast of a | ||
| non-generic `JsonTypeInfo` β and the options set a `TypeInfoResolver` (e.g. | ||
| `DefaultJsonTypeInfoResolver`) so the call doesn't throw `NoMetadataForType`. | ||
| - [ ] Probing requests use `TryGetTypeInfo<T>(out β¦)` β no `try`/`catch` around | ||
| `GetTypeInfo`. | ||
| - [ ] The program was actually run (`dotnet run β¦`), exited 0, and its printed JSON shows | ||
| the expected property names (e.g. `"Name"`, `"Age"`). | ||
| - [ ] If a **file-based app** (`dotnet run app.cs`) is used, every `JsonSerializerOptions` | ||
| sets a `TypeInfoResolver` β file-based apps disable reflection so plain serialization | ||
| throws `NoMetadataForType` without one. | ||
|
|
||
| ## Common pitfalls | ||
|
|
||
| | Pitfall | Fix | | ||
| | --- | --- | | ||
| | Hand-rolling a `class β¦ : JsonNamingPolicy` for PascalCase | Delete it; set `PropertyNamingPolicy = JsonNamingPolicy.PascalCase`. | | ||
| | Adding `[JsonPropertyName("Name")]` to every member to force casing | Remove the attributes; the naming policy handles all members at once. | | ||
| | Casting `(JsonTypeInfo<T>)options.GetTypeInfo(typeof(T))` | Call the generic `options.GetTypeInfo<T>()`; no cast needed. | | ||
| | `try { options.GetTypeInfo<T>(); } catch (β¦) { β¦ }` to test availability | Replace with `if (options.TryGetTypeInfo<T>(out var info)) { β¦ }`. | | ||
| | `NotSupportedException` / `NoMetadataForType` from `GetTypeInfo<T>()` | The options have no resolver. Set `TypeInfoResolver = new DefaultJsonTypeInfoResolver()` (reflection) or a source-generated `JsonSerializerContext` (trim/AOT). | | ||
| | `NoMetadataForType` even for a plain `Serialize` in a `dotnet run app.cs` file-based app | File-based apps disable STJ reflection. Add `TypeInfoResolver = new DefaultJsonTypeInfoResolver()`, or run it as a normal project instead. | | ||
| | Leaving the app on the SDK's default TFM | Pin `net11.0` explicitly so the .NET 11 APIs resolve and the output shows the target. | | ||
| | Claiming success without running | Run `dotnet run` and paste the actual JSON output; the target is a working, executed program. | | ||
|
|
||
| ## More info | ||
|
|
||
| - [JsonNamingPolicy class](https://learn.microsoft.com/dotnet/api/system.text.json.jsonnamingpolicy) β built-in naming policies including `PascalCase` | ||
| - [JsonSerializerOptions.GetTypeInfo](https://learn.microsoft.com/dotnet/api/system.text.json.jsonserializeroptions.gettypeinfo) β typed and non-typed metadata access | ||
| - [JsonTypeInfo\<T\>](https://learn.microsoft.com/dotnet/api/system.text.json.serialization.metadata.jsontypeinfo-1) β strongly-typed serialization metadata | ||
| - [DefaultJsonTypeInfoResolver](https://learn.microsoft.com/dotnet/api/system.text.json.serialization.metadata.defaultjsontypeinforesolver) β reflection-based resolver required by `GetTypeInfo`/`TryGetTypeInfo` | ||
| - [File-based apps](https://learn.microsoft.com/dotnet/core/sdk/file-based-apps) β `dotnet run app.cs` and the `#:property` directive | ||
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.