We’re changing how “Ignore empty constraints” works when 1) the constraint type is “is in” or “isn’t in” and 2) the constraint value is an empty list.
In the past, here’s how these constraints were evaluated with an empty list as the value:
|old||“is in”||“isn’t in”|
|“Ignore empty constraints” true||false||true|
|“Ignore empty constraints” false||false||false|
Here’s a table of how these constraint types will behave in the future when the value is an empty list (with changes italicized):
|new||“is in”||“isn’t in”|
|“Ignore empty constraints” true||true||true|
|“Ignore empty constraints” false||false||true|
We hope this will make the constraints work in more intuitive fashion!
In the next few days, we’ll be deploying this functionality in a new version of Bubble that you will have to upgrade to in the “Settings” tab of the editor, under “Versions”. We’re deploying this as a new version because, if your app uses search constraints fitting the above description, this change will affect your app’s behavior – so please double-check your constraints before upgrading!