-
Notifications
You must be signed in to change notification settings - Fork 451
chore: enable package-comments
linter with exceptions for existing violations
#1720
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1720 +/- ##
==========================================
+ Coverage 67.50% 67.51% +0.01%
==========================================
Files 172 172
Lines 16242 16242
==========================================
+ Hits 10964 10966 +2
+ Misses 4603 4601 -2
Partials 675 675 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
I think the linter is doing its work - we need to add comments to these packages. |
@cuixq yup that's the next step - I'm going to be working on that in the background, but its currently a low priority |
This pull request has not had any activity for 60 days and will be automatically closed in two weeks |
not stale, just have not gotten around to it yet 😅 |
b69082f
to
05091e7
Compare
f1ce24d
to
544740d
Compare
544740d
to
9cb7314
Compare
package-comments
package-comments
linter with exceptions for existing violations
Spent a bit of time to just add comments to all the offending packages. Closes: #1720 --------- Co-authored-by: Gareth Jones <jones258@gmail.com> Co-authored-by: Xueqin Cui <72771658+cuixq@users.noreply.github.com>
While it looks ugly, this means new packages will have to pass this lint and we can chip away at the existing ones rather than having to deal with them all at once