-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Provide meta data to custom merge functions #33
Labels
Resolution: Added
This has been added to the project.
Status: Released
It's now live.
Type: Feature
New features or options.
Comments
This was referenced Feb 10, 2022
Closed
RebeccaStevens
added
the
Status: In Progress
Issue is currently being resolved by a developer.
label
Feb 10, 2022
RebeccaStevens
added a commit
that referenced
this issue
Feb 13, 2022
…customized fix #33 BREAKING CHANGE: custom function call signatures have changed
RebeccaStevens
added a commit
that referenced
this issue
Feb 14, 2022
…customized fix #33 BREAKING CHANGE: custom function call signatures have changed
RebeccaStevens
added a commit
that referenced
this issue
Feb 14, 2022
…customized fix #33 BREAKING CHANGE: custom function call signatures have changed
RebeccaStevens
added a commit
that referenced
this issue
Feb 14, 2022
…customized fix #33 BREAKING CHANGE: custom function call signatures have changed
RebeccaStevens
added a commit
that referenced
this issue
Feb 14, 2022
RebeccaStevens
added a commit
that referenced
this issue
Feb 14, 2022
RebeccaStevens
added a commit
that referenced
this issue
Feb 14, 2022
RebeccaStevens
added a commit
that referenced
this issue
Feb 14, 2022
RebeccaStevens
added a commit
that referenced
this issue
Feb 14, 2022
Closed
🎉 This issue has been resolved in version 3.0.0-beta.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
RebeccaStevens
added a commit
that referenced
this issue
Feb 16, 2022
RebeccaStevens
added a commit
that referenced
this issue
Feb 16, 2022
github-actions bot
pushed a commit
that referenced
this issue
Feb 16, 2022
# [3.0.0-beta.5](v3.0.0-beta.4...v3.0.0-beta.5) (2022-02-16) ### Features * provide customizable meta data to custom merge functions ([f6b1cad](f6b1cad)), closes [#33](#33)
🎉 This issue has been resolved in version 3.0.0-beta.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
RebeccaStevens
added a commit
that referenced
this issue
Feb 17, 2022
RebeccaStevens
added a commit
that referenced
this issue
Feb 17, 2022
RebeccaStevens
added a commit
that referenced
this issue
Feb 17, 2022
RebeccaStevens
added a commit
that referenced
this issue
Feb 18, 2022
RebeccaStevens
added a commit
that referenced
this issue
Feb 19, 2022
github-actions bot
pushed a commit
that referenced
this issue
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`
🎉 This issue has been resolved in version 3.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
RebeccaStevens
added
Resolution: Added
This has been added to the project.
and removed
Status: In Progress
Issue is currently being resolved by a developer.
labels
Feb 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Resolution: Added
This has been added to the project.
Status: Released
It's now live.
Type: Feature
New features or options.
Suggestion
When merging values, it is not uncommon that meta data is need to know how to merge the values. An example would be that values may want to be merged differently if they are under a certain key on a record.
By default, key meta data should be provided by this library.
Users should also have the ability to control/customize the meta data as the deepmerge function steps through.
An example of customizing the meta data would be to mark a flag at some point through the merge to customize how child elements are then merged. An other example would be to keep track of the full key path travelled by the function.
The text was updated successfully, but these errors were encountered: