feat: add pullObject
#576
Merged
feat: add pullObject
#576
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
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 9939ef5:
|
cjquines
reviewed
Mar 19, 2024
cjquines
approved these changes
Mar 21, 2024
|
🎉 This PR is included in version 1.56.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 2.0.0-beta.7 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
A new function the suite of object-creating utilties. Pull provides a simpler API for mapToObj style mappings where both the key and the value need to be computed from an iterable of items.
Make sure that you:
src/index.tsmapping.mdWe use semantic PR titles to automate the release process!
https://conventionalcommits.org
PRs should be titled following using the format:
< TYPE >(< scope >)?: descriptionAvailable Types:
feat: new functions, and changes to a function's type that would impact users.fix: changes to the runtime behavior of an existing function, or refinements to it's type that shouldn't impact most users.perf: changes to function implementations that improve a functions runtime performance.refactor: changes to function implementations that are neitherfixnorperftest: tests-only changes (transparent to users of the function).docs: changes to the documentation of a function or the documentation site.build,ci,style,chore, andrevert: are only relevant for the internals of the library.For scope put the name of the function you are working on (either new or
existing).