Monday, March 10, 2025
1 change · saas-17.4
Enhancements to existing features
The web domain editor now preserves user-friendly filter options inside nested conditions when filters are edited elsewhere. This prevents criteria such as “Active is not set” from being unintentionally converted to a less accurate equivalent, reducing confusion and keeping saved rules consistent.
Original PR description
In order to be created, virtual operators like "is", "not_set" need field definitions to be known. It turns out that in sub trees corresponding to sub domains for any/not_any operators), the virtual operators are not created because: - the option getFieldDef is not passed when constructing sub trees - the getFieldDef function does not collect info on paths in sub trees. Here we solve each problem so that when modifying the tree in some way all virtual operators are restored correctly. For instance if a condition involving a boolean field like "Active is not set" is found in a sub tree, and a condition is added/removed elsewhere, the above condition will remain the same and not become "Active = False".