This issue lists the planned work items for the next few releases. This list exists so you know where this project is headed and how I will probably spend my time. Tasks are not ordered by priority. I might not strictly follow the roadmap if something else needs to be addressed earlier or is a low-hanging fruit.
If you'd like to see another feature on this list, let's discuss this in the comments below.
Goals
Increasing productivity and ease of use
Things that bother me and would also make this project more useful for a broader audience.
[x] enable fixes in LanguageService plugin
[ ] #316 introduce code actions
[x] #255 Angular integration
Accessibility for new users / documentation overhaul
Restructuring and rewriting the existing documentation to make it actually useful. Top priority are new users. Rule authors are also a high priority target. Feedback is very welcome.
[ ] #746 Make documentation easier for new users
[ ] #17 add missing documentation for all features
Tap into ESLint ecosystem
ESLint has a vast amount of (mostly) useful rules. Combined with Wotan's understanding of TypeScript (default excluded files, caching, potentially watch mode, ...) this might become more useful than typescript-eslint.
[ ] #517 allow using ESLint rules
[ ] Enable use of existing ESLint configuration
[ ] probably goes along with configuration overhaul #635
Features and Stability
[ ] #760 Cache should track rules accessing other source files
[ ] #479 Watch mode
[ ] Allow rules to access the file system through RuleContext
This issue lists the planned work items for the next few releases. This list exists so you know where this project is headed and how I will probably spend my time. Tasks are not ordered by priority. I might not strictly follow the roadmap if something else needs to be addressed earlier or is a low-hanging fruit.
If you'd like to see another feature on this list, let's discuss this in the comments below.
Goals
Increasing productivity and ease of use
Things that bother me and would also make this project more useful for a broader audience.
Accessibility for new users / documentation overhaul
Restructuring and rewriting the existing documentation to make it actually useful. Top priority are new users. Rule authors are also a high priority target. Feedback is very welcome.
Tap into ESLint ecosystem
ESLint has a vast amount of (mostly) useful rules. Combined with Wotan's understanding of TypeScript (default excluded files, caching, potentially watch mode, ...) this might become more useful than typescript-eslint.
Features and Stability