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
When the new concurrent mode supported version is released could you also publicly export useOperator?
Right now in one of my projects i am using the useSubjectValue to merge subscription data with custom state and update it using a reducer style approach (via the update method)
From the concurrent mode pull request i noticed that you have replaced useSubjectValue with useOperator and once it is realease i would not be able to update my code unless i fork the hook
Thanks
The text was updated successfully, but these errors were encountered:
Yes, it’s our intention to move this back to either react-wonka or create a more generic hook package. We’ve merged this to master only so we can test Wonka 4 and this new hook together properly
Edit: also please note that if you’ve been relying on useSubjectValue providing synchronous updates, that’ll change back to run normal effects are the initial mount.
This is because we’d like to move back to cooperatively scheduling urql’s logic with React’s effects.
As for the Edit part no i was not expecting synchronous updates. As already explained i was merging subscription data with custom state and update at the same time using a reducer approach style.
When the new concurrent mode supported version is released could you also publicly export useOperator?
Right now in one of my projects i am using the useSubjectValue to merge subscription data with custom state and update it using a reducer style approach (via the update method)
From the concurrent mode pull request i noticed that you have replaced useSubjectValue with useOperator and once it is realease i would not be able to update my code unless i fork the hook
Thanks
The text was updated successfully, but these errors were encountered: