The problem
Any value can be saved into any configuration. A retention period accepts -1, a threshold accepts 999999, an email pattern accepts something that is not an email — and the application finds out at the point of use rather than at the point of entry.
What we have in mind
Validation rules declared per configuration and enforced in the editing UI:
- Integer ranges
- Date ranges
- String patterns (regex)
Open question worth comments: whether a rule that rejects a value already stored should block saving unrelated changes, or just flag it.
Opened from our own backlog when this tracker went public. If you need this, say so — comments and concrete use cases are what move something up the list.
The problem
Any value can be saved into any configuration. A retention period accepts
-1, a threshold accepts999999, an email pattern accepts something that is not an email — and the application finds out at the point of use rather than at the point of entry.What we have in mind
Validation rules declared per configuration and enforced in the editing UI:
Open question worth comments: whether a rule that rejects a value already stored should block saving unrelated changes, or just flag it.
Opened from our own backlog when this tracker went public. If you need this, say so — comments and concrete use cases are what move something up the list.