-
Notifications
You must be signed in to change notification settings - Fork 23
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
build: add eslint-plugin plugin to project's lint config #708
build: add eslint-plugin plugin to project's lint config #708
Conversation
This change adds the `eslint-plugin-eslint-plugin` recommended config to the project's lint configuration, and disables the current 25 errors, for addressing as follow-up changes.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #708 +/- ##
==========================================
- Coverage 98.92% 98.85% -0.08%
==========================================
Files 17 17
Lines 1120 1135 +15
Branches 113 113
==========================================
+ Hits 1108 1122 +14
- Misses 12 13 +1 ☔ View full report in Codecov by Sentry. |
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.
@all-contributors please add @michaelfaith for infra.
|
I've put up a pull request to add @michaelfaith! 🎉 |
Adds @michaelfaith as a contributor for infra. This was requested by JoshuaKGoldberg [in this comment](#708 (comment)) --------- Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
This change resolves all of the violations revealed by JoshuaKGoldberg#708, except for one. The messages used to report violations in `valid-package-def` are coming from PJV and not maintained by the plugin. So unless there's an attempt to map PJV errors to statically defined messages within the rule, that one will need to continue using `message`
<!-- 👋 Hi, thanks for sending a PR to eslint-plugin-package-json! 💖. Please fill out all fields below and make sure each item is true and [x] checked. Otherwise we may not be able to review your PR. --> ## PR Checklist - [x] Addresses an existing open issue: fixes #81 - [x] That issue was marked as [`status: accepting prs`](https://github.com/JoshuaKGoldberg/eslint-plugin-package-json/issues?q=is%3Aopen+is%3Aissue+label%3A%22status%3A+accepting+prs%22) - [x] Steps in [CONTRIBUTING.md](https://github.com/JoshuaKGoldberg/eslint-plugin-package-json/blob/main/.github/CONTRIBUTING.md) were taken ## Overview This change resolves all of the violations revealed by #708, except for one. The messages used to report violations in `valid-package-def` are coming from PJV and not maintained by the plugin. So, unless there's an attempt to map PJV errors to statically defined messages within the rule, that one will need to continue using `message`. I took my best stab at defining the `type` property for the ones that were missing it. Let me know if you think any of them should be adjusted. Closes: #81
🎉 This is included in version v0.19.0 🎉 The release is available on: Cheers! 📦🚀 |
PR Checklist
status: accepting prs
Overview
This change adds the
eslint-plugin-eslint-plugin
recommended config to the project's lint configuration, and disables the current 25 errors, for addressing as follow-up changes.Closes #82