You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/*eslint-disable-next-line some-linter/some-very-long-rule-name -- This disable requires an explanation that can easily be made so consise that it would fit under a limit of 80 chars. Triggering eslint(max-len) in theprocess*/
This leads to eslint-disable-next-line multiline comment that can vary wildly in style and format.
Some things to consider:
Spacing around start/end markers
indentation of newlines
Whether comment should start on the second line
Newline after start marker / before end marker?
I feel like this could safely be taken care of by a formatter.
Atm, with manual formatting, I try to aim for a concise but consistent
/* eslint-disable-next-line some-linter/some-very-long-rule-name --This disable requires an explanation that can easily be made so consisethat it would fit under a limit of 80 chars. Triggering eslint(max-len) inthe process */
(I don't expect dprint to word-wrap, a line-length linter rule and manual fixes already take care of that)
The text was updated successfully, but these errors were encountered:
See the following multiline comment. There are no rule that I know of which can enforce consistent formatting for it. Neither https://eslint.org/docs/latest/rules/multiline-comment-style , nor https://github.com/eslint-community/eslint-plugin-eslint-comments (I've open the same issue there: eslint-community/eslint-plugin-eslint-comments#161 )
This leads to eslint-disable-next-line multiline comment that can vary wildly in style and format.
Some things to consider:
I feel like this could safely be taken care of by a formatter.
Atm, with manual formatting, I try to aim for a concise but consistent
(I don't expect dprint to word-wrap, a line-length linter rule and manual fixes already take care of that)
The text was updated successfully, but these errors were encountered: