I don’t believe there is any difference between true and checked at all.
There is however a difference between false and not checked, in that not checked covers both the false and empty states. Whereas false does not cover the empty state.
The important thing to be aware of is that Glide booleans have 3 possible states:
- true
- false
- empty, or null
The default state for a boolean when it is first created will be empty, and it will return to empty if you clear it with a set column values action. That state is neither true or false. This is something that often trips people up when they start testing for false and don’t get the results that they expect - because they aren’t aware (or forget about) the 3rd state (empty).
This is why many of us advise against testing for false, and instead test for either true or not true.
I see checked/not checked as interchangeable with true/not true. It’s just a convenience thing.
When it comes to case, testing that I’ve done suggests that case is unimportant.
That is, true == True == TRUE == tRuE
But of course it’s better to be consistent. My preference is to always use all lower case.
Here is a short video that highlights the difference between true, false and empty: