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
Unpack todo/warning comments #39
Conversation
Show the warning comments right in the terminal. Also, will truncate all messages now based on terminal width. For unpacked warning comments, will drop the ruleId before truncating.
2775c45
to
ec29f0a
Compare
The { ruleId: 'no-warning-comments',
severity: 1,
message: 'Unexpected \'todo\' comment.',
line: 197,
column: 61,
nodeType: 'Line',
endLine: 197,
endColumn: 118 } From linting: https://github.com/avajs/ava/blob/c3bcbf2a568c12017fe0da041dc247a226019001/lib/babel-pipeline.js#L197 |
Interesting. Is there a rhym or reason to that? Should we try to recover the comment in that case? |
Seems you're using an undocumented property. The |
Also note:
So if there's no |
Confirmed: eslint/eslint@27e3f24 |
Oh crap. Unfortunately, our existing test fixtures don't have what I need to test this properly. I've got a busy next week and a half, but I'll try to get to it next weekend. Come on GitHub. We need reminders! |
Agreed! For now, you can go to https://github.com/notifications/read, find the notification for this issue, and click "Save for later". Or click "Mark as unread" here if you use Refined GitHub. |
Ping :) (If you're busy, no worries. Just pinging in case you just forgot about it) |
Closing in favor of sindresorhus/eslint-plugin-unicorn#401. Better and easier to fix the rules instead. |
Show the warning comments right in the terminal.
Also, will truncate all messages now based on terminal width.
For unpacked warning comments, will drop the ruleId before truncating.
Fixes: #27