-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
feat(experimental-utils): use mergable interface for settings
property
#3556
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
feat(experimental-utils): use mergable interface for settings
property
#3556
Conversation
Thanks for the PR, @G-Rath! 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. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day. |
Nx Cloud ReportCI ran the following commands for commit 3bc6a8c. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch
Sent with 💌 from NxCloud. |
Nx Cloud ReportCI ran the following commands for commit fdf79a1. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch
Sent with 💌 from NxCloud. |
* Plugins can add their settings using declaration | ||
* merging against this interface. | ||
*/ | ||
// eslint-disable-next-line @typescript-eslint/no-empty-interface |
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.
isn't this unnecessary now?
i'm surprised our lint rule didn't fire on this
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.
okay weird... none of the checks ran on your last commit
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.
quite right, and yeah, that is weird...
I'll rebase to resolve the conflict and remove this at the same time, which'll hopefully trigger CI.
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 like you conflicted with your previous PR!
otherwise LGTM
Codecov Report
@@ Coverage Diff @@
## master #3556 +/- ##
=======================================
Coverage 92.63% 92.63%
=======================================
Files 325 325
Lines 11236 11236
Branches 3168 3168
=======================================
Hits 10409 10409
Misses 367 367
Partials 460 460
Flags with carried forward coverage won't be shown. Click here to find out more.
|
This lets us do declaration merging to define settings at the plugin level e.g.