Files
twenty/packages
sonarly-bot ceb07b709b fix(workflow): handle IS_NOT_NULL in filter evaluator
https://sonarly.com/issue/40432?type=bug

A workflow run crashed in the filter action because the runtime evaluator throws on operand

Fix: I fixed the root cause by adding support for `ViewFilterOperand.IS_NOT_NULL` in the default filter evaluator:

- Updated `evaluateDefaultFilter` so `IS_NOT_NULL` falls through to the same behavior as `IS_NOT_EMPTY` (`isNotEmptyTextOrArray(leftValue)`).
- This prevents runtime throws like `Operand IS_NOT_NULL not supported for string filter type` when default/string-like filters resolve through the fallback evaluator.
- Added a regression test in the filter evaluator spec for unknown/default filter type:
  - non-empty left operand + `IS_NOT_NULL` => `true`
  - null/empty left operand + `IS_NOT_NULL` => `false`

This keeps backward compatibility with operand conversion (`isNotNull` -> `IS_NOT_NULL`) and matches existing operand semantics used across other filter evaluators.

Authored by Sonarly by autonomous analysis (run 46094).
2026-05-25 03:38:47 +00:00
..
2026-05-04 11:09:34 +02:00