🎉 Better Boilerplate by Not Quite Unicorns - Our take on what a good Bubble app looks like

[akamarski]

when you have 1 is 1, you don’t have to validate if the first is empty. Else the condition fails => 0 is not 1

when you have 1 (but can be 0) = 1 (but can be 0) you have to validate that the first one isn’t 0, else it can enter a 0 is 0 state and expose data to anonymous visitors who also have 0 as their value

Careful using only Current User's X in privacy rules

The other scenario this happens is when deleting data. If, for example, you delete an Organisation, and forget to delete some data related to that Organisation (let’s say, it’s Invoices), then the Organisation field on the Invoice would become empty. This is probably the most common scenario that could make a breach like this occur.

The trick is with the “Current User” because it has another layer of variability - whether is logged in or not.