Update eslint-plugin-shopify #1086
Merged
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
Add a linting check to ensure we always use `<React.Fragment>` over `</>` Remove deprecation notices that are no longer triggered (see jsx-eslint/eslint-plugin-react#2069)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
WHY are these changes introduced?
We recently got bit by using
<>instead of<React.Fragment>. We should always use<React.Fragment>and people shouldn't be expected to remember that.WHAT is this pull request doing?
<React.Fragment>over</>Disable legacy lifecycle methods linting in scope of
no-deprecatedrule for now jsx-eslint/eslint-plugin-react#2069)How to 🎩
Ensure linting passes