Part of story #36833 search on semantics and always there fields even if not defined No functional change. CI should be happy. Notes: I reused the same "checker" as Title, as the checks are exactly the same for both. Why ? This is part of the refactoring of 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. Change-Id: Ic286f97a1d402da8245d9fa331b8ad4055587a88

+11 −11

Author

Joris MASSON (jmasson) 2024-03-22 14:30

Committer

Joris MASSON (jmasson) 2024-03-22 15:14

Hash 4d929e389e85627e84f7d95a03fd2e4cb2abebbb

Parent b9de6d0b67fef1ea103d6d04b3b3a2616473cd5f

Reference git #tuleap/stable/4d929e389e85627e84f7d95a03fd2e4cb2abebbb