-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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: handle nullish coalescing operator in exhaustive-deps rule #8146
Conversation
Ensure that the exhaustive-deps rule correctly handles cases where the nullish coalescing operator (??) is used in query functions. Example test case:
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 4e1774a. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 2 targetsSent with 💌 from NxCloud. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8146 +/- ##
=========================================
+ Coverage 0 87.82% +87.82%
=========================================
Files 0 15 +15
Lines 0 493 +493
Branches 0 183 +183
=========================================
+ Hits 0 433 +433
- Misses 0 46 +46
- Partials 0 14 +14
|
fixes #8131
Ensure that the exhaustive-deps rule correctly handles cases where the nullish coalescing operator (??) is used in query functions.
Example test case: