Eslint/key spacing #653
Closed
Eslint/key spacing #653
Conversation
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
http://eslint.org/docs/rules/key-spacing enforce consistent spacing between keys and values in object literal properties This rule enforces spacing around the colon in object literal properties. It can verify each property individually, or it can ensure horizontal alignment of adjacent properties in an object literal.
Contributor
|
@sarupbanskota this is the default in suave? |
Contributor
|
@sarupbanskota bump. |
Contributor
|
Hi @sarupbanskota just wanted to check in since it sadly seems like we're out of date now by a lot (lots of conflicts 😢 ). Do you want me to close this? |
Contributor
Author
|
Yes @joshsmith, let's close this one for now. |
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.
What's in this PR?
Setup rules for
key-spacingand fixed it for existing codebase.Make sure any changes to code include changes to documentation.
References
Progress on: #599