Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[App Rotuer] Inconsistent Client Scope with shallow app routing #32

Open
Krakazybik opened this issue Jul 20, 2024 · 0 comments
Open

[App Rotuer] Inconsistent Client Scope with shallow app routing #32

Krakazybik opened this issue Jul 20, 2024 · 0 comments

Comments

@Krakazybik
Copy link

Krakazybik commented Jul 20, 2024

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:

image

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant