Use object shorthand for properties #219
Merged
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
58 tasks
toddbluhm
approved these changes
Apr 30, 2020
|
I was just going to say, maybe merge this after: #213? |
|
Will do ✔️ |
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.
What is the purpose of this pull request? (put an "X" next to item)
[ ] Documentation update
[ ] Bug fix
[ ] New feature
[x] Other, please explain: lint update
What changes did you make? (Give an overview)
I started using object shorthand for properties, that is, I changed
eslint: eslinttoeslint.Which issue (if any) does this pull request address?
standard/eslint-config-standard#166
Is there anything you'd like reviewers to focus on?
The three lines changed 😅
Compatibility: This is supported on Node.js >=4, and we are using
Object.assignwhich also became available in that version ✅