Be able to save any parameter as undefined

[lorensansol]

Hello!

I use Hugo and it is common for me to use merge between different objects so that, if a parameter is not defined, it will take by default the one of the previous object with the same name.

This is useful for me in the CMS to set default values.

For this reason I need to be able to save any parameter as undefined or null, regardless of the widget type.

With Static CMS I do this through custom widgets, by adding a ❌ (x mark) type button in the corner of each widget, which allows to change the value of that parameter to undefined.

I am aware that custom widgets do not yet exist.

I wonder if it would be possible and reasonable for you to add an equivalent option, within the 3-dot menu in each widget, (for example, next to another option called Revert Changes), that would do this. It could be called Remove Value, for example.

For this it would be important not to autofill boolean fields. It seems to me that it would make more sense for this to be the case if "required": false is specified. If not, perhaps an output.booleans_default_false option would work, for example.

The output.omit_empty_optional_fields option does not work for me, as I must be able to:

• Indicate an empty string '' in the text fields to overwrite possible upper non-empty strings.
• Indicate false in the boolean fields to overwrite possible higher true values.

[kyoshino]

I think you need to use custom widgets also in Sveltia CMS. The support for custom widgets is coming in Q2.