A more than a year passed, any progress on that?

Are you saying that Strapi does not have a way for a custom field to be validated? I am talking about actual content creating/editing phase when user clicks Save or Publish buttons, not the phase of adding a new custom field with base & advanced tabs.

I am creating a custom field with tested select options (5 items) each depends on previous select choice. That content field has json storage type. Examle: Audi -> A7 -> 4K -> 3.0 TSFI. I do not have a sophisticated validation rules, I just want to have first 3 Selects required to be filled. Any thoughs how to show user a simple message about that?

I created a collection type which had white spaces in API ID fields. Strapi showed no validation error, but I couldn't save the collection and stuck at that step forever, unless I delete the collection and re-create it.

I think, Strapi should, at least, has a white spaces check for API ID fields.

Thanks,

This will be Great Feature. :-)

Yeah it would be really good to be able to write custom field and entity level validations that are displayed in the UI and returned through API.

Some validation examples:

* I want to make sure that start date is before end date

* I want to make sure that a field is filled out if another checkbox is checked

* I want to make sure that a number is a multiple of 10

* ...