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
There is no painless and non-deprecated way to invalidate client scope data when using shallow routing.
When navigating to a new page in shallow routing mode, the values in the client scope are not updated if they have changed to default values, because serialize returns only the modified values and hack inject updates the values based on them.
Process Illustration:
Screen.Recording.2024-07-20.at.19.06.43.mov
Expected Result:
During navigation, if the value of any store has been changed to the default value, it should be invalidated in the client scope.
Problem:
There is no painless and non-deprecated way to invalidate client scope data when using shallow routing.
When navigating to a new page in shallow routing mode, the values in the client scope are not updated if they have changed to default values, because serialize returns only the modified values and hack inject updates the values based on them.
Process Illustration:
Screen.Recording.2024-07-20.at.19.06.43.mov
Expected Result:
During navigation, if the value of any store has been changed to the default value, it should be invalidated in the client scope.
Reproduction:
https://github.com/Krakazybik/effector-shallow-routing-inconsistency/tree/main
The text was updated successfully, but these errors were encountered: