Replies: 1 comment
-
I somehow totally missed this, and there's some really great points in here! I'll go through and make some issues and see what I can do. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After having betterer part of our project for quite a while, I thought I should clean up the rules a bit, check which ones I can remove from the betterer config and instead re-enable in our regular eslint config and so on.
But... not sure how to do that... because there's no way to see what rules are actually currently broken?
The results file doesn't mention which rule is broken anywhere, only the text from the rule failing, which isn't always obvious. Sometimes it's fairly easy to guess if you have an example, like "Missing return type on function." is probably "@typescript-eslint/explicit-function-return-type", but I have no idea what error message to look for with the rule "@typescript-eslint/restrict-plus-operands" for example, and not sure what rule "Unexpected value in conditional. A boolean expression is required." belongs to.
Any chance of making this easier somehow?
Really wish each line in the results file would include the name of the rule, so it was easy to "map". It would also be very helpful with a "summary-mode" of some sort, to list out which rules in the betterer-tests are no longer needed. Not sure if any of these are possible though... but hope so, because I'm not sure how to proceed now 😛
Beta Was this translation helpful? Give feedback.
All reactions