-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Store devtools show initialstate of a lazy loaded slice of state instead of actual state. #487
Comments
Hi @diegomaninetti, |
Thank's @phillipzada My issue regards the "regression" to the state history BEFORE the module loading. The problem is the difference between the state shown in the first image and the one shown in the second image: they should be identical regardless of the actions dispatched in the meantime. |
@diegomaninetti I think i figured out what is going on here. When you initially load the app you are redirected to NotFound page, i.e root state is loaded. Then when you click "Take Me Home" is redirecting to
This can be seen in the timestamp to the right of the action type it is changed implying a different action entirely. You can if you edit the routerLink property on the not-found component to say I'm not sure if this is an intended angular feature to "reload" when Hope this helps |
@phillipzada, as far as I know, navigating to "/" does not reload application. In any case, I expect that selecting an action will show the status of the store when the action is executed. Thank's |
I'm submitting a...
What is the current behavior?
When a new reducer get loaded with StoreModule.forFeature(), checking the initial state (corresponding to @ngrx/store/init action), the state contains all the initialized states after first loading of the feature reducer.
Expected behavior:
Devtools should show the correct state relative to the selected action in devtools app.
Minimal reproduction of the problem with instructions:
https://github.com/ngrx/platform/tree/master/example-app
(see attached images)
Version of affected browser(s),operating system(s), npm, node and ngrx:
Chrome Version 61.0.3163.100, windows 10, ngrx/* 4.0.x, devtools 2.15.1
The text was updated successfully, but these errors were encountered: