New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support TypeScript in configuration initializer. #11789
Support TypeScript in configuration initializer. #11789
Comments
I'm not opposed if the team consensus is to add support to ESLint init specifically for Typescript. After all, we already explicitly ask about React. However, I'm worried about potentially having to field more requests to add support for Flow or other libraries/frameworks. ESLint was built to get out of the business of legislating rules, and pluggability has been a core design principle in that area. But we haven't done the same with init. So, what I would like us to at least consider is: How can we make ESLint init more pluggable? Is there a way we could let plugins extend our init somehow? If such a thing could be implemented, then I envision typescript-eslint could export a binary in their package which might be something like, |
Personally, I think it might be difficult to have a "pluggable |
You're right. So, IMHO, I prefer scaffolds (something like Yeoman) for new projects and/or new users. |
I can certainly agree that discoverability is both (1) important, and (2) a problem with my proposal. I just don't want to get into the business of being gatekeepers for every single type of init scenario. I'm okay with adding Typescript since its linting is actually a project some of us are trying to support. Just worried that some might see this as precedent. Maybe I'm overthinking it since I could have said the same thing about the React question and we don't get tons of requests to support other libraries in init. |
I am somewhat divergent on the issue: same reasons as @platinumazure we can:
seems b. is more promising! |
Unfortunately, it looks like there wasn't enough interest from the team Thanks for contributing to ESLint and we appreciate your understanding. |
I'm okay with adding Typescript for now. This should be a pretty simple change so I don't think an RFC is required here. I'll reopen this and add it to the TSC agenda. I'm not going to add a TSC Summary/Question because I think the initial post does a good job explaining. |
Unfortunately, it looks like there wasn't enough interest from the team Thanks for contributing to ESLint and we appreciate your understanding. |
The TSC resolved this week to include a built-in TypeScript config preset and look into allowing plugins to provide additional init presets in the future. |
The version of ESLint you are using.
master
The problem you want to solve.
When running
eslint --init
, an option for TypeScript can be provided. Ref: #11368Your take on the correct solution to problem.
Add a question or option in Inquirer questions list.
Are you willing to submit a pull request to implement this change?
Yes.
The text was updated successfully, but these errors were encountered: