You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the callback of a computed property, the computed_depends_on properties are not passed correctly after resetting them.
For example, I have a computed property "__something" which has the computed_depends_on field "a". a has the default value of 5.
When the module is loaded for the first time, 5 is correctly passed to the callback function in the $args array (first argument of the function).
When I change a to 1, then 1 is correctly passed.
When I then remove the value of a, the builder displays 5 (greyed out), the field is basically empty. a in the callback function is now not 5 but empty as well.
When I change a back to something different, the reset button appears. Resetting it (at least on text fields) will now actually write 5 into the field. I can also write 5 in the field myself and the reset button disappears again. Now 5 is passed to the callback.
Some other fields behave strange as well like dropdowns and buttons. I think is this is a general problem and will apply to all field types.
The text was updated successfully, but these errors were encountered:
In the callback of a computed property, the computed_depends_on properties are not passed correctly after resetting them.
For example, I have a computed property "__something" which has the computed_depends_on field "a". a has the default value of 5.
When the module is loaded for the first time, 5 is correctly passed to the callback function in the $args array (first argument of the function).
When I change a to 1, then 1 is correctly passed.
When I then remove the value of a, the builder displays 5 (greyed out), the field is basically empty. a in the callback function is now not 5 but empty as well.
When I change a back to something different, the reset button appears. Resetting it (at least on text fields) will now actually write 5 into the field. I can also write 5 in the field myself and the reset button disappears again. Now 5 is passed to the callback.
Some other fields behave strange as well like dropdowns and buttons. I think is this is a general problem and will apply to all field types.
The text was updated successfully, but these errors were encountered: