Nullables feature request

[DomenPigeon]

Could the library start using nullables in the source code? Otherwise its really hard to know what is initialized and what not or you need to check everything.

For example:

var container = new V1Container();
container.VolumeMounts.Add(new V1VolumeMount());

produces:
Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object.

[tg123]

i agree and i am also attempting to migrate everything to struct

[foriequal0]

How does migrating everything to struct help that?
Nullable structs have poorer DX than nullable reference types that are assisted by flow analysis,
easier to make mistakes like modifying the copy, make more boxing, bad for performance, ...
It's not recommended by the c# guideline https://learn.microsoft.com/en-us/dotnet/standard/design-guidelines/choosing-between-class-and-struct

[foriequal0]

Google products' API conventions typically don't map well for C#.

They prefer to use json:"...,omitempty" tag, and I suspect that it's due to the lack of discernible differences in both Golang's behavior on nil/empty slices (https://stackoverflow.com/a/44305910/3176773) and their protobuf spec/codegen behavior.

However, popular JSON parsers (Netwonsoft Json, System.Text.Json) don't have such a feature by default.
The C# codegen of protoc avoids this problem by assigning an empty default collection (RepeatedField, MapField) for all array/map fields, and custom json parser/serialization implementation.
Although it lacks nullable reference annotations, it is fairly consistent and usable enough on nullness (it's little bit tricky, though). Primitive type fields always have a default value, object type fields can be null, collection fields are never null.