-
Notifications
You must be signed in to change notification settings - Fork 405
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(store): patch operator must handle existing nulls #2064
fix(store): patch operator must handle existing nulls #2064
Conversation
Changed patch operator not fail when the existing value is null by using a null save access to the key of the object fixes ngxs#2063
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 5db904a. 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 3 targetsSent with 💌 from NxCloud. |
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.
Thank you so much for the contribution!
Just 2 tweaks to tests.
Co-authored-by: Mark Whitfeld <markwhitfeld@users.noreply.github.com>
BundleMon (Integration Projects)Unchanged files (1)
Total files change -3B 0% Final result: ✅ View report in BundleMon website ➡️ |
Code Climate has analyzed commit 5db904a 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.5%. View more on Code Climate. |
* fix(store): made patch operator handle existing null nicely Changed patch operator not fail when the existing value is null by using a null save access to the key of the object fixes #2063 * Apply suggestions from code review Co-authored-by: Mark Whitfeld <markwhitfeld@users.noreply.github.com> --------- Co-authored-by: Mark Whitfeld <markwhitfeld@users.noreply.github.com> (cherry picked from commit bd067dd)
Changed patch operator not fail when the existing value is null by using a null save access to the key of the object
fixes #2063
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
When the existing value of the patch operator is null/undefined it causes a key access error
Issue Number: #2063
What is the new behavior?
Does not throw an error if existin is null/undefined
Does this PR introduce a breaking change?
Other information