FEATURE: Do not apply NotEmptyValidator if the field is hidden about neos-ui HOT 1 OPEN

Hi, I just want to add some informations ;)

there is actually a plan to introduce the concept of required properties like

type: string
required: true

neos/neos-development-collection#4304

this was intended as replacement for NotEmptyValidator and would be enforced directly by the content repository. That would also mean, that your proposed hidden logic could not be accounted for that low level.

My point is I actually want to move away from this super soft validaton (which is currently only triggered by the ui, and invisible to the cr) to a much stricter enforcement. And I’m not sure that these validators are the future and if we should introduce concepts like this to make nodes less strict.

(Our conditional hidden properties are a thorn in my eyes in general- even if I very much like them and use them - imagine your php model which is called ‚Thing‘ which has a lot of properties and it’s implicitly known that when x is set to bar that y must be also set … such models are not fun to work with and don’t tell from the best architecture, but in nodes we might not always have better options)

Edit: for now you might be able to implement a custom ValidateIfNotHidden validator or something;)

from neos-ui.