Not long ago, we introduced the feature ‘validate by expression’. This feature made it possible to build custom validations to model properties based on an expression. However, we wanted to go a few steps further with this feature. Here is what we did:
- You can now build multiple expressions to validate a model property.
- The expressions are sortable to decide which must be executed first.
- Each expression can hold a custom message to preview to the end user when the given value is invalid.
- Validation errors (and their messages) can be caught/ fetched by an after_validation action. This feature can be very helpful for example in import events. When import lines aren’t imported (because some are invalid) you want to know why.
Advanced model property validations with their messages to preview and catch
We made a learn article about this new feature. Soon we will provide you with howto tutorials in which we explain this feature even more.
