This is especially true for dynamic forms. Say I have an entity Project, with properties Company and ContactPerson, both with a NotNull contraint

When I create a form for this, the type will have one normal field: company, and one field that is added by a listener, depending on the chosen company: contactPerson.

If I would post to this form without supplying values for either field, I will get two errors. One is mapped to the company field as expected. The other error, however, should be mapped to contactPerson, which, however, does not yet exists. Instead the error bubbles up to the top and atop the form it will just show "This value should not be null".

Especially if there's a lot of dependant fields on your form, this will quickly become a mess above the form.

I would like to see a way to handle these situations a bit better, for example adding the propertypath to the error message if it is not mapped to it directly. Although this will look quite technical to the end user, it's still better than nothing.