-
-
Notifications
You must be signed in to change notification settings - Fork 387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prevent-abbreviations: Fix objects must not be overlapped in a report. #912
Comments
@sindresorhus if you are interested these crashing rules could be identified by scheduled smoke tests. I can setup PR if this seems useful. |
Is it similar to our integration test? |
I'm going to add |
Looks quite similar. It clones given repositories and runs ESLint on files of the repository. Files are also filtered based on file size, file exclusion pattern and file extension. Tests are run on multiple threads via I've included this ESLint plugin to my scheduled CI runs. These are ran against 150 repositories, but for a single ESLint plugin it can easily be run against 500-1000 repositories for fairly short time. So far these scheduled runs have spotted three issues from this plugin. You might want to add their repositories in your tests as well.
|
Have you run this on |
https://github.com/AriPerkkio/eslint-remote-tester/actions/runs/400370452
|
That's fast! |
This sounds great to me. Would be nice to be able to test even more repos. @AriPerkkio Do you plan to actively maintain |
I've ran
I sure do! I find this project very exciting. It's become very powerful tool for testing various ESLint plugins. |
We could maybe set it to run a limited number of repos for each PR/commit and also create a GitHub Actions cron job that runs once a week which runs a huge amount of repos. Then the run time doesn't matter. |
How about still run on these repos in this file for PRs. |
Yes, that's what I meant. But many more repos in addition once a week. |
Hello, I'm testing stability of well known community ESLint plugins with
eslint-remote-tester
. This ESLint plugin seems to contain a rule which causes linter to crash. ESLint rules should not crash in any condition since this makes all valid linting problems disappear. If this is a false flag please let me know.This issue was spotted by automated CI run: https://github.com/AriPerkkio/eslint-remote-tester/runs/1487452403
Crashing rule:
prevent-abbreviations
If name of the
VariableExpression
and name of theTSTypeReference
are identicalunicorn/prevent-abbreviations
crashes.Minimal repro:
This seems to be valid typescript:
https://www.typescriptlang.org/play?#code/JYOwLgpgTgZghgYwgAgApQPYAdkG8BQyRywAJgFzIgCuAtgEbQDc+AvvvghiAM5hqYsldNmQBePCQrIAjMlYt8EAB5YMUfqQjxqAG34isTIA
This causes ESlint to dispaly an error:
Errors from real-world projects
Rule: prevent-abbreviations
Fix objects must not be overlapped in a report. Occurred while linting <text>:1
microsoft/fluentui/packages/codemods/src/modRunner/tests/mocks/MockMods/CodeMod.mock.ts
Rule: prevent-abbreviations
Fix objects must not be overlapped in a report. Occurred while linting <text>:1
microsoft/fluentui/packages/fluentui/docs/src/components/ComponentDoc/ComponentPropsTable/ComponentPropsTable.tsx
The text was updated successfully, but these errors were encountered: