Error Message Misleading: 'Field Must Not Be Empty' on Optional Property Fields

[carikan]

Current: When creating a new entry, if you click on the "not mandatory" property fields, you get the warning "field must not be empty". It is confusing, the only way to get rid of it for the user, seem to be deleting the property.

Suggestion: The warning "field must not be empty" should not appear for the optional properties.

[stefanprobst]

these fields are pre-added in the edit forms because they are part of a list of "recommended" fields. either filling them out, or intentionally deleting a field is currently the intended behavior.

from the app's point of view there is currently no way to distinguish between pre-populated "recommended" fields, and property fields manually added by a user, in which case we do want to show an error message if left blank.

before changing the behavior it may be good to revisit the list of recommended fields, i.e. if we really need all of those.

also, a help text could be added to clarify. wdyt?

[mkrzmr]

connected to #179

[vronk]

couldn't we relax the validation, to allow (or ignore?) empty fields? (irrespective of prepopulated vs. manually added.)

[laureD19]

Can we change the help text "Field must not be empty" to "This is a recommended field. Add something here if you can."

Is it possible to make this sentence yellow instead of red?