Consistent empty / null fields about rest-layer HOT 4 OPEN

@Dragomir-Ivanov, FYI.

What do you think?

from rest-layer.

@smyrman I think we need to consider also Default fields. What happens if you omit in regular PATCH a field with Default value. Does it stay the same, is it deleted, or it is reset to its default value.
I think regular PATCH syntax as very limited.
I like the idea of having fields as not set and set to empty, but still haven't used that, nor mixed rest-layer with TS (but planning a rewrite to TS asap).

from rest-layer.

Good ponits @Dragomir-Ivanov.

If files are omitted on PUT (a.k.a update), then yes, reset to default values. If they are explicitly set to nil on PUT, then clear them. This can be done as both operations would be handled by the Validation step, but would not work if the same resource is sent to validation multiple times.

When fetching the resource back out, they will be either omitted or null based on the resource config.

from rest-layer.

PS! we might need to make sure that PATCH results always serialize (the original) resource before calculating changes / base.

from rest-layer.