You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Right now, you have to deliberately look for linter exceptions by searching for each individual linter's exception rules. This isn't exactly a problem, but is a little annoying.
Describe the solution you'd like
We could use an action for a test that always passes but lists out all the current exceptions to linter rules across all files to increase the visibility of linter exceptions for ease of finding and removal.
Describe alternatives you've considered
We could also do a big cleanup push and then fail on new exceptions, but that feels draconian and might require us to delay merges from upstream in some cases. We could also just keep searching for each linter when we have time to do some cleanup, which is fine but annoying and subject to human error.
Additional context
Improving the visibility of linter exceptions would allow us to more easily locate those places and find ways to accomplish our goals without making as many exceptions to the linter rules. This could help us have cleaner and more consistent code.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Right now, you have to deliberately look for linter exceptions by searching for each individual linter's exception rules. This isn't exactly a problem, but is a little annoying.
Describe the solution you'd like
We could use an action for a test that always passes but lists out all the current exceptions to linter rules across all files to increase the visibility of linter exceptions for ease of finding and removal.
Describe alternatives you've considered
We could also do a big cleanup push and then fail on new exceptions, but that feels draconian and might require us to delay merges from upstream in some cases. We could also just keep searching for each linter when we have time to do some cleanup, which is fine but annoying and subject to human error.
Additional context
Improving the visibility of linter exceptions would allow us to more easily locate those places and find ways to accomplish our goals without making as many exceptions to the linter rules. This could help us have cleaner and more consistent code.
The text was updated successfully, but these errors were encountered: