[brianrourkeboll]

Workaround for #129.

• Enable RespectNullableAnnotationsDefault and RespectRequiredConstructorParametersDefault globally in this repo. (The tests in this repo targeting .NET 9 or higher fail at this commit.)
• Disable JsonSerializerOptions.RespectNullableAnnotations and JsonSerializerOptions.RespectRequiredConstructorParameters in code for the JsonSerializer instance used in this library when targeting .NET 9 or higher, which takes precedence over the global switches in this repo and in any consuming code.

If and when the nullable annotations are fixed, the two explicit disablings should be removed.

[HofmeisterAn]

Thanks for the issue and the PR. The model classes are generated by tools/specgen, and the bug is there. It only marks pointers and omitempty fields as nullable, but Go also writes nil maps and slices as null.

I think it's better to fix the generator than to turn the switches off in the library, because that would hide the wrong annotations. It would also make them correct at compile time for consumers.

[brianrourkeboll]

I think it's better to fix the generator than to turn the switches off in the library

Yes, if we can make the annotations accurate, that would be best. And once they are accurate, we would want to turn these switches on, as in the first commit here (they're off by default for backwards compatibility).