-
Notifications
You must be signed in to change notification settings - Fork 332
Return no updates when performing an NX set to an existing array element #593
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
Related comment |
@EricRabil Thank you for your fix. It looks good. We will be happy to merge it once tests are added. |
Awesome. I'll add tests within the next day |
@oshadmi tests have been added, let me know if you'd like any changes to be made to them. |
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.
Minor addition.
Thanks!
Co-authored-by: Omer Shadmi <76992134+oshadmi@users.noreply.github.com>
@oshadmi do you have any additional changes for me to make? |
Codecov Report
@@ Coverage Diff @@
## master #593 +/- ##
==========================================
+ Coverage 82.99% 83.02% +0.03%
==========================================
Files 11 11
Lines 3116 3123 +7
==========================================
+ Hits 2586 2593 +7
Misses 530 530
Continue to review full report at Codecov.
|
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.
👍🏼
This PR addresses #592, although I'd like some feedback from other contributors on how I fixed it as I'm not sure if this is intentional behavior.
This does not modify the mutations made to the document, but instead stops returning an out-of-range error when doing an NX set to an array element that is, in fact, in range.