An empty yes/no field evaluates to no

[emir.ozgun]

Sometimes it is not about ‘‘considered to be fixed’’ but fixing that may break lots of apps. In this case yes/no defaulting to no suddenly can break so many apps, but lets say new date picker, bubble can natively add in addition to old date picker.

[ihsanzainal84]

@boston85719

For some other reasons to not leave them blank for no, is that when you export your data as CSV or JSON the field value DOES NOT show as false, it shows as empty.

I never noticed this!

[randomanon]

@boston85719

Remember, that False is not the same as Null and so an empty yes/no field is not the same as No.

Actually for my use case, it is.

@boston85719

I’ve been building in Bubble for 7.5 years, 6.5 of them professionally. I’ve clocked in over 10,000 hours of development time.

And yet you don’t use parentheses in your dynamic expressions. Bizarre.

[boston85719]

@randomanon

Actually for my use case, it is.

@emir.ozgun

In this case yes/no defaulting to no suddenly can break so many apps

The discussion is not about making yes/no fields default to no as some sort of fix. The discussion is that a dynamic expression using a data field of type yes/no that is empty, does evaluate to no…

@randomanon

Actually for my use case, it is.

[emir.ozgun]

Yeah yeah I know my bad. But you get the idea