Why are descriptions / comments mandatory for save-and-restore nodes?

[DenSinH]

Like the title says. We are tempted to remove this restriction. Of course, a good description for a configuration / snapshot is good to have, but sometimes (at least in testing) we want to just create nodes without having to enter a description. Is there another reason why this field is mandatory?

[georgweiss]

Names on resources are in most cases not sufficient to determine what they contain or represent. One obvious side-effect is that such resources tend to stick around forever as nobody dares to delete them.

Comments also help in search.

All in all, in my view the restriction is essentially about data management. But having a customizable preference setting to relax the restriction is fine with me.

[georgweiss]

@DenSinH, please feel free to create a PR where the restriction to add a comment can be relaxed through a preference setting. Default should be to keep the restriction, i.e. relaxing it must be explicitly set in a local preference file.