fix: bump deepmerge dependency fixing optimistic updates #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
haddowg
changed the title
haddowg
changed the title
|
Thanks, I will take a look later hopefully today, that it does not break any tests. I must really setup CI btw :) |
|
Is it possible also for you to give me the code snippet which actually failed? So I will write regression test |
|
Merged and released yesterday, thanks for the contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bump to use the latest deepmerge, I have kept this pinned to latest rather than using
^as this was the existing convention.Specifically, this will resolve an issue I experienced with optimistic updates of objects with falsey values fixed in 4.2.1, see
TehShrike/deepmerge#172