Object.assign documentation and tests #115
Closed
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.
This took me a while because I wrote some tests to experiment and got the source and target mixed up - the mutable target goes first. Should we have labels on these?
I attempted to write code for
assignMany
but it doesn't work because you can't create an array of objects with different types. Well you can I guess if they start off as Object.empty() or are imported - jumping through hoops. Will this really get used? Do we need atoGenericObject
function?I couldnt' figure out the other flavor of assign with the json thing and what it does.