We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm playing with utilizing the Source Generator approach in the Json Serializer in order to optimize performance of informers.
Benefits of this approach:
See these two docs:
Unfortunately, I've hit a snag due to the existing Json converters being internal.
Options:
KubernetesJson.AddJsonOptions(x => x.TypeInfoResolver = JsonTypeInfoResolver.Combine(SourceGenerationContext.Default, JsonSerializerOptions.Default.TypeInfoResolver)); [JsonSerializable(typeof(V1Node))] [JsonSerializable(typeof(V1Namespace))] .. add all other types internal partial class SourceGenerationContext : JsonSerializerContext { }
Thoughts?
The content you are editing has changed. Please copy your edits and refresh the page.
The text was updated successfully, but these errors were encountered:
it is so cool, it is worth to have those converters public
Sorry, something went wrong.
merge into #1395
Successfully merging a pull request may close this issue.
I'm playing with utilizing the Source Generator approach in the Json Serializer in order to optimize performance of informers.
Benefits of this approach:
See these two docs:
Unfortunately, I've hit a snag due to the existing Json converters being internal.
Options:
Thoughts?
Tasks
The text was updated successfully, but these errors were encountered: