You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use the example oldArrayMerge() code given in the README but it won't run, as cloneIfNecessary() and isMergeableObject() are not defined. I see that isMergeableObject() can be got from another package (though it would be much neater if deepmerge could expose it as a pass-through), but cloneIfNecessary() doesn't seem to be defined anywhere.
My code depends on the pre-2.0.0 behaviour for array merging, so it would be really helpful to be able to reproduce this on the latest 2.0.0 code.
Thanks for this tool; it is very helpful, and I also appreciate the efforts you have gone to to explain how to keep the pre-2.0.0 behaviour; hope this issue report helps with that.
The text was updated successfully, but these errors were encountered:
Good point. And relatedly, there's no example code executing that function - if there was, then jsmd would have caught the error when running the automated tests.
I did have a quick look at your build process, noticed jsmd and wondered what it did—sounds very helpful, and could be of use in a few projects on which I work; thanks :-).
* Roll back to deepmerge 1.5.x due to change in behaviour
TehShrike/deepmerge#83
* Add command definition for main-landmark.
* Add translation text for main-landmark.
* Simplify command handling in background script.
* Make error throwing consistent.
I'm trying to use the example
oldArrayMerge()
code given in the README but it won't run, ascloneIfNecessary()
andisMergeableObject()
are not defined. I see thatisMergeableObject()
can be got from another package (though it would be much neater if deepmerge could expose it as a pass-through), butcloneIfNecessary()
doesn't seem to be defined anywhere.My code depends on the pre-2.0.0 behaviour for array merging, so it would be really helpful to be able to reproduce this on the latest 2.0.0 code.
Thanks for this tool; it is very helpful, and I also appreciate the efforts you have gone to to explain how to keep the pre-2.0.0 behaviour; hope this issue report helps with that.
The text was updated successfully, but these errors were encountered: