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 there any chance you can look into switching to eslint as well? I think this plugin would be very beneficial! I don't like to switch to typescript-eslint before I found an override-implementation.
The text was updated successfully, but these errors were encountered:
This rule was supposed to come out of the box, but nobody wanted to do it. Thanks to @hmil , he took the matter into his own hands and solved for us. It would be better if the new project adopted this in their own project early on.
Thanks for bringing this up. I guess someone needs to investigate what it would take to port this plugin to eslint. Maybe eslint exposes the same interface to the type system and then most stuff can be reused. Or they expose something completely different and then it's better to write a new plugin from scratch.
It could be useful to keep both plugins in the same repo though such that design discussions about the override keyword itself can be focused in the same place.
The TypeScript project has announced that they're shifting focus to eslint from tslint
Is there any chance you can look into switching to eslint as well? I think this plugin would be very beneficial! I don't like to switch to typescript-eslint before I found an override-implementation.
The text was updated successfully, but these errors were encountered: