-
Notifications
You must be signed in to change notification settings - Fork 406
fix(store): memoize selectors which return NaN #2230
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
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit b09342e. 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 4 targetsSent with 💌 from NxCloud. |
commit: |
In this commit, we update the memoize equality function to correctly check for `NaN` values because we can't use the default `===` comparison operator, as `NaN` is not equal to itself (`NaN === NaN` is false). Additionally, we have added a check using `Number.isNaN`.
BundleMonFiles updated (1)
Unchanged files (5)
Total files change +284B +0.22% Groups updated (2)
Final result: ❌ View report in BundleMon website ➡️ |
BundleMon (NGXS Plugins)Unchanged files (9)
No change in files bundle size Unchanged groups (1)
Final result: ✅ View report in BundleMon website ➡️ |
BundleMon (Integration Projects)Files updated (3)
Total files change +72B +0.03% Final result: ✅ View report in BundleMon website ➡️ |
Code Climate has analyzed commit b09342e and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 95.3% (0.0% change). View more on Code Climate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fantastic work!
In this commit, we update the memoize equality function to correctly check for
NaN
values because we can't use the default
===
comparison operator, asNaN
is not equalto itself (
NaN === NaN
is false). Additionally, we have added a check usingNumber.isNaN
.