Skip to content
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

feat: lone values will now be passed to mergeOthers rather than just returned #57

Merged
merged 1 commit into from
Feb 18, 2022

Conversation

RebeccaStevens
Copy link
Owner

Previously if a value had nothing to be merged with, it would just be used as the result. Now it is
instead passed to the mergeOthers function so that the result can be customized if wanted

…returned

Previously if a value had nothing to be merged with, it would just be used as the result. Now it is
instead passed to the mergeOthers function so that the result can be customized if wanted

BREAKING CHANGE: The `mergeOthers` function will now be passed lone values, make sure your custom
version can handle these cases.
@RebeccaStevens RebeccaStevens added Type: Feature New features or options. Breaking Change This change will require a new major release. labels Feb 18, 2022
@RebeccaStevens RebeccaStevens merged commit 14a09ca into next Feb 18, 2022
@RebeccaStevens RebeccaStevens deleted the single-item-merge branch February 18, 2022 16:58
RebeccaStevens added a commit that referenced this pull request Feb 18, 2022
…returned (#57)

Previously if a value had nothing to be merged with, it would just be used as the result. Now it is
instead passed to the `mergeOthers` function so that the result can be customized if wanted
github-actions bot pushed a commit that referenced this pull request Feb 18, 2022
# [3.0.0-beta.7](v3.0.0-beta.6...v3.0.0-beta.7) (2022-02-18)

### Features

* lone values will now be passed to mergeOthers rather than just returned ([#57](#57)) ([14a09ca](14a09ca))
RebeccaStevens added a commit that referenced this pull request Feb 18, 2022
…returned (#57)

Previously if a value had nothing to be merged with, it would just be used as the result. Now it is
instead passed to the `mergeOthers` function so that the result can be customized if wanted
RebeccaStevens added a commit that referenced this pull request Feb 19, 2022
…returned (#57)

Previously if a value had nothing to be merged with, it would just be used as the result. Now it is
instead passed to the `mergeOthers` function so that the result can be customized if wanted
RebeccaStevens added a commit that referenced this pull request Feb 19, 2022
…returned (#57)

Previously if a value had nothing to be merged with, it would just be used as the result. Now it is
instead passed to the `mergeOthers` function so that the result can be customized if wanted
github-actions bot pushed a commit that referenced this pull request Feb 19, 2022
# [3.0.0](v2.0.1...v3.0.0) (2022-02-19)

### Code Refactoring

* unrequire unused types and values ([c78e373](c78e373))

### Features

* lone values will now be passed to mergeOthers rather than just returned ([#57](#57)) ([9c24584](9c24584))
* provide customizable meta data to custom merge functions ([3d96692](3d96692)), closes [#33](#33)

### BREAKING CHANGES

* some types have changed for `deepmergeCustom`
@RebeccaStevens RebeccaStevens added Resolution: Added This has been added to the project. Status: Released It's now live. labels Feb 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Breaking Change This change will require a new major release. Resolution: Added This has been added to the project. Status: Released It's now live. Type: Feature New features or options.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant