-
Notifications
You must be signed in to change notification settings - Fork 99
working proposal for autofix based on eslint example #47
Conversation
… communication between client/server
…sLintCode is not unique.
@rlasjunies thanks, I took a quick look at the code and it looks promising. I need more time for a deeper look. I think we would get more quick fixes if the tslintautofix.ts becomes part of tslint, the way you wrote the code it is independent of VS Code. @unional, @jkillian what do you think? |
Hi all, auto-fixing problems is a feature that we'd like to have in TSLint, although as far as I know, there's been no implementation work on it (outside of this anyways). It would probably be best to have a short proposal written up there documenting what sort of API a feature like this would have and basic implementation ideas over in palantir/tslint#561 |
@jkillian makes sense to start with an API proposal. @rlasjunies do you have the cycles for this? we could also involve @dbaeumer given his autofix work for eslint. I'll still look into make this PR available in the tslint extension so that we get feedback from users on the auto fix UI support. |
@rlasjunies I'll reopen since I still want to look into it and will try to make it available as is so that we get feedback from users. This is independent of whether the autofixes come from tslint or here. |
The PR looks good, thanks @rlasjunies ! |
This was announced in today's update for VSC, but doesn't seem to be shipped? |
Thanks for the reminder. Published the version as 0.5.25. |
Hi @egamma,
As proposed here is the PR for tslint autofix.
Work pretty fine for now.
Let me know your feeling.
BR