Right now, when testing the syntax of a filter, all we do is disable short circuit evaluation and parse it. While this could seem a sane approach, it has underlying bugs which cause some patterns to fail with actual parsing (i.e. short-circuit enabled), but be reported as correct by the syntax checker.
Syntax checking should probably use a different strategy and avoid fully parsing the code, with or without short-circuit enabled. T204654 is related.
Description
Description
Related Objects
Related Objects
- Mentioned In
- T204654: Find a better way to compute variables when testing filter syntax
T228677: use of get_matches function returns "Requesting array item of non-array"
T224746: [Beta Commons] All attempts to upload with UploadWizard fail - Mentioned Here
- T214674: Short circuit fails with assignments
T218906: Short-circuit evaluation fails with multiple comparisons
T204654: Find a better way to compute variables when testing filter syntax
T214642: Short circuit breaks with multiple operations