Closed seebs closed 1 year ago
oh, good catch. i'll fix that too while i'm looking at it.
oh. d'oh. that one's my fault from the trackexistence stuff.
hah. i was just thinking "huh we don't have a test case for max being less than min. well, surely it works." i was wrong.
good catch.
Kudos, SonarCloud Quality Gate passed!
0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells
No Coverage information
0.0% Duplication
parseOperand was assuming that any reference to MIN in a place where an operand was expected was a call, which it should be, but it might not be. parseCallExpression panics if it doesn't find a parenthesis, because it's never supposed to be called when we don't know we have one.
The test for this is in with MinMaxColumnConstraints, even though it's actually a test of MinMaxFunctionCalls, because that's where the other tests involving the special MIN/MAX tokens live.