Repository navigation
add case-police checks, fix case issues - #3052
Merged
Merged
Conversation
✅ Deploy Preview for react-native ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
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
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.
This PR adds the
case-policecheck to the workspace.It has been attached to the
lanuage:lintscripts. I have also decided to filter out abbreviates dict (https://github.com/antfu/case-police/tree/main/dict), since it leads to too many false-positives in path, especially for Android (SDK, URI etc.).The issues can be fixed automatically, just like most of ESLint warnings, by adding
--fixflag at the end of script/command.The changeset also includes all of the fixes listed by
case-policeafter the initial configuration.