docs: switch Typed Linting docs to project service #9614
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. |
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 11e8579. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 2 targetsSent with 💌 from NxCloud. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## v8 #9614 +/- ##
=======================================
Coverage 88.01% 88.01%
=======================================
Files 401 401
Lines 13637 13637
Branches 3960 3960
=======================================
Hits 12003 12003
Misses 1325 1325
Partials 309 309
Flags with carried forward coverage won't be shown. Click here to find out more. |
PR Checklist
Overview
Goes through our first-run docs to suggest
parserOptions.projectServiceinstead ofparserOptions.project.For the FAQs files, splits into Project Service Issues and Traditional Project Issues headings, respectively.
Does not update the parser package's docs themselves (
/packages/parser#projectservice). I'm still waiting on performance investigations to know how to frame things (#9571).💖