Only serialize properties that have been assigned

[NickStrupat]

Currently, ZeroQL will serialize a model to JSON text with all the properties, regardless of whether or not they've been assigned, except properties that have a value of null.

This is a problem for any nullable properties that should, during a mutation, be assigned to a value of null.

I propose that models should track which properties have been assigned, and only properties that have been assigned should be in the resulting payload to the server.

Below is an example of a possible implementation of what the generated model code would be...

class Foo
{
    private readonly Dictionary<string, object> assignedProperties = new(); // all models would have this field

    private string? text;
    public string? Text { get => text; set => assignedProperties["Text"] = text = value; }

    private int count;
    public int Count { get => text; set => assignedProperties["Count"] = text = value; }
}

And then whenever serialization happens, it would serialize foo.assignedProperties instead of foo itself.

[NickStrupat]

Hmm, that implementation idea wouldn't really help for the opposite: querying partial entities.

This might need something like Optional<T> for each property.

[byme8]

I saw that the StrawberryShake graphql client from HotChocolate is doing something similar like your first suggestion.

I have been thinking about adding it but never got a good use-case while using the ZeroQL.

[NickStrupat]

What about making a base class/interface for generated DTOs, and making it partial.

That way folks could add custom logic/validation with things like https://github.com/Fody/PropertyChanged. What I proposed could be implemented with that, I'm pretty sure...