Single Validation
Single validation vs collection of validations
This choice is not UI fluff. It fundamentally changes how your rule behaves, how errors are reported, and how users should interpret results.
Single validation
You are answering one question:
"Does this element comply with rule X?"
Characteristics:
- One condition
- One validator
- One error message
- Pass or fail per element
This is the right choice for 70% of all rules.
Typical use cases:
- Required parameter exists
- Value is in an allowed list
- Value matches a regex pattern
- Boolean is true or false
- Numeric value is within a range
If you are unsure, start here.
Why single validations are preferred
Single validations are:
- easy to name clearly
- easy to report on
- easy to fix — the user knows exactly what is wrong
- easy to combine: several single validations on the same filter are still single validations
A rule that tries to check three things at once is not a "thorough rule" — it is a rule that is harder to fix, harder to explain, and harder to trust.
What a single validation looks like in DAQS
Filter: selects FamilySymbols in category Doors
Validation: assemblyCode — Not empty
Name: "Assembly Code must be filled"
One filter. One validator. One name. One error per failing element.
When to use a collection instead
Use a collection of validations when multiple checks belong to the same contractual requirement and should be reported together.