Since the if statement checks for ‘True’ its good to be consistent
1 Like
bump bump…
Seeing that I’m not the only person upset by this 
I think there should be some uniformity across Tulip.
Either “YES/NO” or “TRUE/FALSE” not a mix of both.
I don’t mind either terminology as long as they are consistent.
This is a long standing one that kinda irks me too!
I just wrote a fresh feature request for this, to see if we can’t get a fresh set of eyes on it. I totally agree this is one thats an incredibly quick win (1 line of code). It has been a known gap, but most of our engineering focus has been on improving the product in more tangible ways.
Pete
