feat(parser): always enable comment, loc, range, tokens#8617
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. |
| project?: string[] | string | boolean | null; | ||
| projectFolderIgnoreList?: (RegExp | string)[]; | ||
| range?: boolean; | ||
| projectFolderIgnoreList?: string[]; |
There was a problem hiding this comment.
I haven't verified yet (typescript-eslint/examples#9), but it looks to me like we never actually supported the RegExp case?
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## v8 #8617 +/- ##
==========================================
+ Coverage 87.33% 87.98% +0.64%
==========================================
Files 387 397 +10
Lines 13024 13881 +857
Branches 3771 4086 +315
==========================================
+ Hits 11375 12213 +838
- Misses 1358 1368 +10
- Partials 291 300 +9
Flags with carried forward coverage won't be shown. Click here to find out more.
|

BREAKING CHANGE: Changes opt-in options from
@typescript-eslint/parserto always-on.PR Checklist
Overview
Hardcodes those values to
trueinparser, and sets up the types so that generated ASTs always have thecomment,range, andtokens.Note that this doesn't change the values in
typescript-estree. That package still has the genericASTtype with conditional types on'comment'and'token'.Adds some more unit tests while I'm in the area.
Co-authored-by: @bradzacher
💖