Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
Closed
Description
Before You File a Documentation Request Please Confirm You Have Done The Following...
- I have looked for existingopen or closed documentation requests that match my proposal.
- I haveread the FAQ and my problem is not listed.
Suggested Changes
Our Troubleshooting & FAQs page athttps://typescript-eslint.io/troubleshooting/ has grown to quite a few FAQs. I'm personally finding it hard to read through. We've also had a few questions on the Discord & issue tracker lately that have been pretty directly answered by those FAQs. That leads me to think they've gotten to the point of unwieldiness where users aren't feeling confident reading & searching through them.
Proposal: let's delineate them into sections? Like, "Typed Linting Setup", "Working with JavaScript", "Performance Troubleshooting"(which is already split out!), etc.?