feat(rule): object-curly-spacing never #68
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.
Proposed rule change:
object-curly-spacingfromalwaystonever, alsoreact/jsx-curly-spacingfromalwaystoneverThe rules we have now it's not consistent, we set
object-curly-spacingtoalwaysbut withobjectsInObjectsset tofalse, which makes the following valid(Note the spacing is asymmetric considering in the end there's no space, but there is a space after opening curly brace)
Same for our
react/jsx-curly-spacingrule, we set it toalwaysbutspacing: { objectLiterals: 'never' }, which makes the following valid:This PR turns both rule to
neverwhich eliminates all unnecessary spaces and confusions. It also makes code more compact and easier to read and author.References:
object-curly-spacing
react/jsx-curly-spacing