additional template schema for validation exceptions #815
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To localize an ERXValidationException there are currently five different localization keys which are checked in a specific order:
The problem is if you have an entity with several properties which should give you the same localization for a specific exception type you need either:
The latter one avoids many duplicate keys but often you would like to restrict that localization to a specific entity and not changing it for all entities.
This patch adds a new template key Entity.Type to realize that which gives a modified order: