aot-json-serializer-context

You can generate an AOT JsonSerializerContext for Refitter contracts using Roslyn to accurately parse types and namespaces, ensuring correct serialization contexts without relying on regex-based type discovery.

Roslyn parses contracts to handle nested types and namespace paths, emitting Outer.Inner structures. It registers only closed generic usages to avoid open generic registrations in the serialization context.

Yes, you can emit [JsonSerializable(typeof(...))] attributes on a proper partial context class within the contracts namespace, supporting both single-file and multi-file generation paths for the serializer context.

Regex-based type discovery lacks the semantic accuracy needed for complex C# structures. Using Roslyn to parse contracts ensures correct handling of nested types, namespaces, and closed generic usages for AOT serialization.

You need an AOT JsonSerializerContext for generated C# contracts when requiring strongly-typed serialization contexts to improve serialization performance and type safety, particularly in Ahead-of-Time compilation scenarios.

No, the Skill registers only closed generic usages to avoid open generic registrations, ensuring accurate and compilable [JsonSerializable] attributes for your generated contracts.