Releases: dgreene1/merge-partially
Releases · dgreene1/merge-partially
v2.0.2
v2.0.1
New feature: new API prevents bad data
New Features:
- the
.deep
method protects against bad data cases. Read the detailed explanation here: https://github.com/dgreene1/merge-partially/blob/master/whyShallowInstead.md
Breaking Changes:
- the
mergePartially
function was replaced with an object calledmergePartially
that has a.deep
function and.shallow
- i.e. use
mergePartially.deep
instead ofmergePartially
- see the new F.A.Q. in the readme that explains the difference between
.shallow
and.deep
and why the API was split into two function.
- i.e. use
Commit History:
- Merge pull request #99 from dgreene1/disallowSeedWithOptionalNested d91316f
- adds additional coverage 187eef7
- Merge branch 'master' into disallowSeedWithOptionalNested a5a9c41
- removed test code that I forgot to remove earlier 6989623
- Gives feedback when seed type is not supported in .deep. Also, this introduces the .deep and .shallow split b90178f
- Merge pull request #96 from dgreene1/dependabot/npm_and_yarn/husky-4.3.0 8df1905
- Bump husky from 4.2.5 to 4.3.0 b0ab513
- Merge pull request #94 from dgreene1/makeItEasierToUse d0e0d70
- One of the users wanted to be able to call it when there was no override. Made that easier again like it was 608bec1
Major Release: ability to merge nested/deep objects, increased test coverage, and minor props change
Major Release: ability to merge nested/deep objects, increased test coverage, and minor props change
New Features:
- the ability to merge a nested/deep object
- here's an example / the test case: https://github.com/dgreene1/merge-partially/pull/92/files#diff-6b623d6bcf5e7f06c466aa060ec9c4b6R132
- exposes the
NestedPartial
type as a convenience so you can explicitly type the override object. Example here: https://github.com/dgreene1/merge-partially/pull/93/files#diff-04c6e90faac2675aa89e2176d2eec7d8R70
Breaking Changes:
- I really couldn't come up with a reason why someone would want to avoid passing in an override object. So the second parameter is no longer optional. I would be very surprised if this breaks anyone. But I made this a major version release anyway.