Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
feat(eslint-plugin): [ban-ts-comments] add "allow-with-description" option#2099
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
feat(eslint-plugin): [ban-ts-comments] add "allow-with-description" option#2099
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Thanks for the PR,@dimitropoulos! 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 onhttps://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitorsper day. |
ban-ts-comments ruleban-ts-comments rulecodecovbot commentedMay 25, 2020 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Codecov Report
@@ Coverage Diff @@## master #2099 +/- ##==========================================- Coverage 93.42% 93.41% -0.01%========================================== Files 171 171 Lines 7755 7763 +8 Branches 2215 2219 +4 ==========================================+ Hits 7245 7252 +7- Misses 244 245 +1 Partials 266 266
|
dimitropoulos commentedMay 25, 2020
once this merges, I'm happy to do a follow-up PR where I change the default (since that will have to wait in the PR until 4.0 happens) |
ban-ts-comments ruleban-ts-comments ruleban-ts-comments rulef80ba23 toa4b99d7CompareUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
bradzacher left a comment
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.
pretty straightforward! Thanks for doing this
A few comments
Uh oh!
There was an error while loading.Please reload this page.
bradzacher left a comment
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.
LGTM - thanks for your work!
dimitropoulos commentedMay 31, 2020
great!@bradzacher would now(ish) be a good time to make the (breaking change) PR that sets this option on by default for whenever 4.0 happens? |
bradzacher commentedMay 31, 2020
I think just raise an issue for now, we can tag it and create a milestone to track 4.0 like we did for 3.0. Saves having a PR open for months to rebase :) |
isilher left a comment
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.
Cool! I'm going to add that shiny newallow-with-description setting 🤩
closes#2093