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
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => https://github.com/ngxs/store/blob/master/CONTRIBUTING.md
[ ] Other... Please describe:
Current behavior
RouterNavigation event is fired every time a navigation is initiated. some times navigation action will be canceled due to AuthGuards.
we don't want to update title if Router event canceled. would be nice if you can configure router-plugin module only fire RouterNavigation when NavigationEnd event is fired. or expose more events e.g., RouterNavigationSuccess etc.
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Environment
Libs:
- @angular/core version: 7.0.3
- @ngxs/store version: 3.2.0
Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: v11.1.0
- Platform: Mac
Others:
The text was updated successfully, but these errors were encountered:
@xmlking This issue may have been fixed by PR #895 which has just been released in v3.4.3!
Could you test and confirm if this issue has been fixed or not?
I'm submitting a...
Current behavior
RouterNavigation
event is fired every time a navigation is initiated. some times navigation action will be canceled due to AuthGuards.Expected behavior
we don't want to update
title
if Router event canceled. would be nice if you can configurerouter-plugin module
only fireRouterNavigation
whenNavigationEnd
event is fired. or expose more events e.g.,RouterNavigationSuccess
etc.Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Environment
The text was updated successfully, but these errors were encountered: