workspace: migrate to eslint-plugin-alex from stand-alone CLI
#4898
+53
−51
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
✅ Deploy Preview for react-native ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Why
After integrating
case-policechecks within ESLint, the only stand-alone CLI/check which left was alex (for insensitive writing language). Unfortunately, I have learned that there is no ESLint plugin for that to, so I have created one:Using it through ESLint should ease the DX process and allow to see warning immediately in chosen IDE/editor, without a need of running separate command.
How
Migrate to
eslint-plugin-alexfrom stand-alone CLI, move configs, update CI scripts and contributing guide.