Remove redundant object from Object.assign example#27
Merged
Conversation
In the "good" `Object.assign` example, the initial new object is redundant as the defaults are also specified in a new object. This is a bit pedantic, and doesn't change the semantics of the example, just removes an unnecessary object creation.
Owner
|
Oh cool! I tested this out and it doesn't look like it mutates the original config, which is good. Thanks Chris! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In the "good"
Object.assignexample, the initial new object is redundant as the defaults are also specified in a new object.This is a bit pedantic, and doesn't change the semantics of the example, just removes an unnecessary object creation.
Note: I definitely wouldn't have bothered with this if I didn't make #4, and was looking at it anyway 😄