Options defined through feel expressions aren't dynamic

[Skaiir]

Describe the Bug

As seen above, changing the isGood variable does not affect the select's values, which is unexpected

Steps to Reproduce

1. add a checkbox with key isGood
2. add a select with options expression if isGood then [ "good"] else ["bad"]
3. toggle the checkbox and check the select values
4. nothing changes

Expected Behavior

The select's values should be dynamically evaluated.

Environment

• Host Web modeler saas

[Skaiir]

My guess is that we don't recalculate the options every time we open the dropdown.

I see two ways of fixing this:

1. We don't consider performance and recalculate every time
2. We somehow make our feel hook clever enough to recalculate every time a variable changes. This is probably scary to implement.

[pinussilvestrus]

We don't consider performance and recalculate every time

Verified this works via fb055ad

I will add more test coverage for this one and check whether it works sufficiently.

[Skaiir]

While this is not release breaking IMO, there is kind of a nuance with this new options case. Since we can now modify the options at field runtime, we should reset the fields when the proper values are not available. Otherwise we get this:

[Skaiir]

Raised it here: #817