SearchKit - Support operators in conditional css rules

[colemanw]

Overview

SearchKit now allows operators other than = in conditional style rules.

Before

Only = operator supported, pseudofields like row_number not supported.

After

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[colemanw]

@eileenmcnaughton I believe you requested this in some lab issue somewhere.

[colemanw]

retest this please

[eileenmcnaughton]

hmm tests are failing a lot today

[colemanw]

retest this please

[eileenmcnaughton]

test this please

[eileenmcnaughton]

@colemanw this is very cool

I did hit one thing - when doing stuff on a field with an option list the value field remains a drop down list of options even when a text box is more appropriate to the operator

[colemanw]

@eileenmcnaughton I'm working on fixing the issue you noted, but it's turning into a pretty big refactor to improve the field/operator/value dynamic across SearchKit (in css conditions, link conditions, where/on/having clauses, etc.). IMO we should merge this first, and I'll follow up with a new PR for that work.

[colemanw]

@eileenmcnaughton followup PR at #22604