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
Some fixes may break the code but actually reveal errors, e.g. #186.
Then there are fixes that disguise an actual problem, e.g. #181 or #203. These are better fixed manually by the developer.
And then there are fixes that you don't want to happen automatically in your IDE if you use autofix-on-save, e.g. no-debugger.
This proposes adding a new category of fixes that may advertised in IDEs and other integrations. These fixes will not be automatically fixed with --fix.
TBD
What does the API look like?
introduce a Failure class that has setters for regular fixes and suggested fixes?
introduce a Fix class with a category field
addFailure would then accept any number of fixes as variadic argument.
allows a failure to suggest different fixes for the same issue
Each Fix needs a name/description so the user knows what it does
Add CLI option to automatically apply all suggested fixes?
How does this work with baseline testing?
The text was updated successfully, but these errors were encountered:
Some fixes may break the code but actually reveal errors, e.g. #186.
Then there are fixes that disguise an actual problem, e.g. #181 or #203. These are better fixed manually by the developer.
And then there are fixes that you don't want to happen automatically in your IDE if you use autofix-on-save, e.g.
no-debugger
.This proposes adding a new category of fixes that may advertised in IDEs and other integrations. These fixes will not be automatically fixed with
--fix
.TBD
Failure
class that has setters for regular fixes and suggested fixes?Fix
class with a category fieldaddFailure
would then accept any number of fixes as variadic argument.The text was updated successfully, but these errors were encountered: