-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
fix(angular-query): forward queryFn errors to the NgZone #8842
Conversation
Not sure if the extra wrapping try...catch is needed 🤔 |
Removed the try...catch wrappers as they were indeed redundant. |
View your CI Pipeline Execution ↗ for commit 066cb8f.
☁️ Nx Cloud last updated this comment at |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #8842 +/- ##
===========================================
+ Coverage 46.60% 88.08% +41.47%
===========================================
Files 200 16 -184
Lines 7574 277 -7297
Branches 1741 44 -1697
===========================================
- Hits 3530 244 -3286
+ Misses 3668 32 -3636
+ Partials 376 1 -375
🚀 New features to boost your workflow:
|
Any errors that occur in the queryFn or mutationnFn that should be thrown in case of
throwOnError: true
should run in theNgZone
, or else the AngularErrorHandler
will not pick them up. A manual try...catch is needed because any errors that occur inside ofngZone.run
are not automatically reported in the zone:This fixes #8839.