Currently, Configurate (with its default configuration implementation) makes it impossible to create a non-virtual empty node. This means, in effect, that you cannot save a null node.
Supporting null values would be useful in a few scenarios. Namely, an optional config option with no default value cannot be saved to the config. This means that the user cannot be made aware of such an option merely by looking at the config, they would have to look at docs or other resources to know of its existence.
Configurate seems to be specifically designed to avoid the creation of non-virtual empty nodes which is why I haven't implemented this myself. The changes would require at least a few fundamental changes to the api.
Currently, Configurate (with its default configuration implementation) makes it impossible to create a non-virtual empty node. This means, in effect, that you cannot save a
nullnode.Supporting
nullvalues would be useful in a few scenarios. Namely, an optional config option with no default value cannot be saved to the config. This means that the user cannot be made aware of such an option merely by looking at the config, they would have to look at docs or other resources to know of its existence.Configurate seems to be specifically designed to avoid the creation of non-virtual empty nodes which is why I haven't implemented this myself. The changes would require at least a few fundamental changes to the api.