Part of story #36833 search on semantics and always there fields even if not defined No functional change. CI should be happy. Why ? Before working on the feature, we need to refactor the structure of the query validation to transition away from checks being grouped by comparison type (equals, lesser than, etc). We want to group checks by semantic / field type instead, as it is easier to understand. Most of the time, we work "field by field", so it makes more sense to have all the business rules for a given field in as few files as possible, instead of having all the business rules for "equals" comparisons being grouped together. Furthermore, usage of inheritance makes it hard to keep a mental model of the validation rules for a given field. To limit risks of regression, we need to add missing unit tests before. Change-Id: Ia7add552aef2d0b842dc6b62c774b735d09514b0

+123 −33

Author

Joris MASSON (jmasson) 2024-03-20 18:16

Committer

Joris MASSON (jmasson) 2024-03-20 18:16

Hash 488ce3ae370fcf510bdbeab2d667f3be719188d1

Parent 3d946ca6a57c98d41a655eeecd5c2b55c710c48a

Reference git #tuleap/stable/488ce3ae370fcf510bdbeab2d667f3be719188d1