-
Notifications
You must be signed in to change notification settings - Fork 331
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
feat: generic linter, absorbing cdot
linter and attribute [instance] in
linter
#12143
base: master
Are you sure you want to change the base?
Conversation
!bench |
Here are the benchmark results for commit b9ee1c4. |
A simple replacement `. --> ·`. See #12143 for the source of these replacements.
A simple replacement `. --> ·`. See #12143 for the source of these replacements.
A simple replacement `. --> ·`. See #12143 for the source of these replacements.
A simple replacement `. --> ·`. See #12143 for the source of these replacements.
A simple replacement `. --> ·`. See #12143 for the source of these replacements.
A simple replacement `. --> ·`. See #12143 for the source of these replacements.
Replace two `.` with `·`. Found by the linter at #12143.
Replace two `.` with `·`. Found by the linter at #12143.
Replace two `.` with `·`. Found by the linter at #12143.
Replace two `.` with `·`. Found by the linter at #12143.
awaiting-author |
Michael, thanks for reviewing! I had intended this PR as an experiment for the "generic" framework and I thought that However, as a further experiment, you can see how now the linter is flexible enough to lint against both |
cdot
lintercdot
linter and attribute [instance] in
linter
🎉 Wow, thanks for rewriting my linter! I see some tension between code duplication and error messages: having all errors be about |
Maybe we could have something like The implementation of the linter would need to handle these refined options. Also, we may have to disengage from |
PR summary bb394346c8Import changes for modified filesNo significant changes to the import graph Import changes for all files
|
A "generic" syntax linter that can be configured using a function
Syntax → Array Syntax
.The expectations is that the function returns sub-syntax extracted from the input that should be flagged by the linter.
This PR provides two examples.
cdot
that are not typed as·
..
with·
#12137is a PR that inspired this one.
attribute [instance] in
that is not limited to the next declaration[Merged by Bors] - feat: lint
attribute [instance] instName in
#13190