Future wish list
Problem
We are almost ready to release 2.0.0, and as such, it's time to start thinking about 3.0.0. As usual, the goal of this issue is to gather feedback on important changes that would be breaking or ambitious. (Other suggestions can just be filed as an issue.) We are already looking at dropping support for Node < 4 in 3.0.0. One thing I'd like to hear is ideas for how can ESLint better support TypeScript and Flow. Note: keep the suggestions as high-level descriptions. This is a brainstorming exercise, we don't want to get into implementation details or plausibility discussions. Let's just see what ideas people have. The best will be explored further. <bountysource-plugin> Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Gather Feedback for ESLint 3.0.0 Enhancements
As we prepare for the release of ESLint 2.0.0, it is essential to gather community feedback on potential breaking changes and ambitious features for the upcoming 3.0.0 version. This includes evaluating how ESLint can better support TypeScript and Flow, which are increasingly popular in the JavaScript ecosystem.
Awaiting Verification
Be the first to verify this fix
- 1
Create a Feedback Collection Document
Set up a collaborative document (e.g., Google Docs or a GitHub issue) where users can submit their suggestions for ESLint 3.0.0. Ensure the document is easily accessible and encourages high-level brainstorming.
- 2
Promote Feedback Collection
Share the document link across ESLint's official communication channels, including social media, mailing lists, and GitHub repositories. Encourage users to contribute their ideas and suggestions.
- 3
Organize a Community Discussion
Schedule a community meeting or webinar to discuss potential features and gather real-time feedback. Use platforms like Zoom or Discord to facilitate this discussion and record the ideas presented.
- 4
Categorize Suggestions
After collecting feedback, categorize the suggestions into themes such as TypeScript support, Flow integration, and other breaking changes. This will help prioritize which ideas to explore further.
- 5
Draft a Summary of Key Suggestions
Compile a summary document that highlights the most promising suggestions for ESLint 3.0.0. This summary will serve as a basis for further exploration and potential implementation in future releases.
Validation
Confirm the fix worked by reviewing the feedback document for active participation and quality of suggestions. Additionally, check attendance and engagement levels during the community discussion.
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep