-
|
Hello. I'm very grateful that you reverted the deprecation of the ".watch" extension, but I'm still having the same issues described in the discussion 😞 Just a reminder, these issues didn't exist before the update that deprecated the ".watch" extension. I'm afraid I'll have to go back to MobX and this is very sad, as I really liked Signas. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
I am not sure the issue you are having currently as the deprecation had nothing to do with the implementation of the watch feature. Also mobx and signals are different libraries with different goals so I would advise making a decision based on project requirements. The watch extension is used to rebuild any Builder scope with a given build context. Most other cases should use the SignalsMixin since it solves a lot of complicated edge cases. The code you shared is a singleton style for all the logic and breaking up the fields to signals would fix the issue you are having. |
Beta Was this translation helpful? Give feedback.
I am not sure the issue you are having currently as the deprecation had nothing to do with the implementation of the watch feature.
Also mobx and signals are different libraries with different goals so I would advise making a decision based on project requirements.
The watch extension is used to rebuild any Builder scope with a given build context. Most other cases should use the SignalsMixin since it solves a lot of complicated edge cases.
The code you shared is a singleton style for all the logic and breaking up the fields to signals would fix the issue you are having.