Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

stable

Clone or download

Read-only

chore: Unit test invalid comparisons and values for float

Download Browse

part of story #10710 search on fields with duck typing No functional change. Unit tests should pass. Why? This will help us refactor the architecture of the invalid checks. We want to transition away from the current state where validation is grouped by comparison type (equals, lesser than, etc.). We want to group it by 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 a few files, instead of having all the business rules for "equals" comparison being grouped together. Change-Id: I1c051814b7b8f07d70426eb74e4402cc021b408b

+76 −2
Joris MASSON (jmasson) 2024-02-19 17:56
Joris MASSON (jmasson) 2024-02-19 17:56
1a1efbf97ab79f7c852b1886103c100609169387
15709a84c47270f079d6b1f9475f56c4cec1d535
git #tuleap/stable/1a1efbf97ab79f7c852b1886103c100609169387

Modified Files

Side by side diff
Inline diff
Name
M plugins/tracker/tests/unit/Tracker/Report/Query/Advanced/InvalidSearchablesCollectorVisitorTest.php +76 −2 Go to diff View file