Skip to content

Remove the last few mentions of tslint in documentation #2003

New issue

Have a question about this project? No Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “No 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? No Sign in to your account

Closed
1 of 5 tasks
Delapouite opened this issue Aug 13, 2021 · 3 comments · Fixed by #2006
Closed
1 of 5 tasks

Remove the last few mentions of tslint in documentation #2003

Delapouite opened this issue Aug 13, 2021 · 3 comments · Fixed by #2006

Comments

@Delapouite
Copy link
Contributor

I'm submitting a...

  • Regression
  • Bug report
  • Feature request
  • Documentation issue or request (new chapter/page)
  • Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Hello!

While reading the documentation pages about the CLI, a few paragraphs still talk about tslint and its configuration files.

Here's an example taken from the page dealing with Monorepo :

image

https://docs.nestjs.com/cli/monorepo

Expected behavior

Tslint is now deprecated. Various tasks have been made codewise to support ESlint along the last months, like this one : nestjs/typescript-starter#69

So, in order to help new-comers in the JS ecosystem and avoid confusion on which linting tool they should be use, I think we should remove the last remaining mention of tslint in the doc, and mention ESLint instead.

If you approve this transition, I could submit a PR to resolve this soon.

Thanks.

@kamilmysliwiec
Copy link
Member

Would you like to create a PR for this?

@Delapouite
Copy link
Contributor Author

Sure! Done.

@kamilmysliwiec
Copy link
Member

Thanks! Let's track this here #2006

No Sign up for free to join this conversation on GitHub. Already have an account? No Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants