[Small performance optimization] boolean operators can now shorthand

[chris.s]

This actually makes a pretty big difference for certain parts of my app that utilize a filtered search for state representations to change icons - where I can organize the multiple conditions by the fastest comparison – a boolean – and not evaluate the complicated search:filtered.

short circuiting is much appreciated - I always wondered if this was implemented on the back end since you’re “building you’re own multi-conditional”.

[chris.s]

if you utilized “Only when A is true AND Get data from an external API” where the API gives you the date - it wouldn’t call that API, and that API may go and do something, log something, calculate something, update something.

Also some plugins may do a calculation when the data is triggered to be read for evaluation, or something else (edge cases) - but it could affect those.