Simplify lintFiles
#583
Merged
Simplify lintFiles
#583
Conversation
This file contains 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
fisker
force-pushed
the
simplify-lint-files
branch
from
228eed8
to
7e0bafd
Compare
|
Thanks for working on this 🙌 |
That would be great 👍 |
This was referenced Aug 7, 2021
devinrhode2
added a commit
to devinrhode2/xo
that referenced
this pull request
Oct 8, 2021
This reverts commit e2e715d.
devinrhode2
added a commit
to devinrhode2/xo
that referenced
this pull request
Oct 8, 2021
This reverts commit e2e715d.
devinrhode2
added a commit
to devinrhode2/xo
that referenced
this pull request
Oct 15, 2021
devinrhode2
added a commit
to devinrhode2/xo
that referenced
this pull request
Oct 15, 2021
devinrhode2
pushed a commit
to devinrhode2/xo
that referenced
this pull request
Oct 15, 2021
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 simplifies the
lintFilesa lot, also changes how config is resolved, but tests are passing, and I ran it over some codebases, it seems works fine.This also fixes a problem described here
There are some follow-up work can do, like DRY, use async api, I can send a separate PR after this get merged.