Loading bar breaks when combined with NGXS
See original GitHub issueI’m having this issue with NGXS and this library. HTTP calls triggered by NGXS Actions make the bar start loading, but it never completes (the bar reaches 100% and doesn’t disappear and the spinner keeps spinning). Manually completing the loading bar with loadingBarService.useRef().complete()
doesn’t help.
Any idea on how to solve this?
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Lazy Loading - NGXS
Stores can be lazy-loaded easily by importing the NgxsModule using the forFeature method. All the other syntax for how you import and describe...
Read more >NGXS - Angular State Management - YouTube
Learn how use an exciting new state management library for Angular. In this episode, we get started with NGXS and compare it to...
Read more >NGXS Storage plugin breaks navigation - Stack Overflow
I am wondering, why the ngxs redirects to homepage when another page is being reloaded? I see in console RouterCancel events.
Read more >Things I Wish I Had Known About Angular When I Started
Split your components into separate modules, so you can import and load only the required modules. The common approach is to divide your ......
Read more >failed to load parser '@angular-eslint/template-parser' - You.com
Any one of those things might have been installed as a slightly different version that now breaks something. Bootstrap, at a guess given...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you for the great work you’re doing on this library! Works perfectly now.
The issue was related to NGXS which runs actions outside of Angular Zone (https://stackoverflow.com/a/58509995/1406096), I’ve pushed a fix in version v5.1.2.
Thanks for the effort!