-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix(eslint-plugin): [class-literal-property-style] allow getter when same key setter exists #8277
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “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? Sign in to your account
Conversation
Thanks for the PR, @yeonjuan! 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. |
38a2136
to
348267b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there's an edge case that needs to be handled? But otherwise this looks good to me!
packages/eslint-plugin/src/rules/class-literal-property-style.ts
Outdated
Show resolved
Hide resolved
7c28999
to
a4cb56f
Compare
…same key setter exists
e7e2b70
to
819b411
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8277 +/- ##
=======================================
Coverage 87.71% 87.72%
=======================================
Files 397 397
Lines 13963 13971 +8
Branches 4061 4065 +4
=======================================
+ Hits 12248 12256 +8
Misses 1403 1403
Partials 312 312
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Aside: could you please not force push PRs? It's a small thing, no worries, but from https://typescript-eslint.io/contributing/pull-requests:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks! 🔥
Just one suggested added test. I can merge this in too to get it in quickly.
#8323 tracks adding a shared utility around the static names. Linking in this comment for tracking.
Oh OK! Sorry about that. I was making the review difficult. 😅 |
No worries at all 😄 TIL I (re-)learned that |
@JoshuaKGoldberg Oops, Maybe this rule should report error on this cases? // group: Record<string, ConfigOptionsType>
group[category] ??= {
heading: category,
fields: [],
}; |
I don't know how that comment got hidden - but, yes - could you take a look please actually? (I'm between things atm) |
@JoshuaKGoldberg I made a pr for fixing it (#8336) |
…same key setter exists (typescript-eslint#8277)
PR Checklist
Overview