docs: mention EXPERIMENTAL_useProjectService in parser package docs #7352
Conversation
|
Thanks for the PR, @JoshuaKGoldberg! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
|
||
| We're hopeful this option will eventually become the standard way to enable typed linting. | ||
| It switches the parser from manually creating TypeScript programs to instead calling the same "project services" API used by editors such as VS Code. | ||
| However, because it's so new and untested, we're keeping it under the `EXPERIMENTAL_` prefix for at least all of the `6.X` versions. |
There was a problem hiding this comment.
fyi @jakebailey, just in case our phrasing is offputting for TypeScript-ers. I have a reminder set to merge this in time for our weekly deployment on Monday.
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #7352 +/- ##
=======================================
Coverage 87.40% 87.41%
=======================================
Files 381 381
Lines 13313 13313
Branches 3934 3934
=======================================
+ Hits 11636 11637 +1
- Misses 1292 1298 +6
+ Partials 385 378 -7
Flags with carried forward coverage won't be shown. Click here to find out more. |
PR Checklist
Overview
Provides a summary of how to use the option, why it's promising, and a back-link to #6754.