Update: Allow eslint-disable-line to be wrapper in BlockComment

[qfox]

What is the purpose of this pull request? (put an "X" next to item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[x] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

Allow to use eslint-disable-line in block-comment as it was in JSCS: /* jscs:ignore */.

Is there anything you'd like reviewers to focus on?

I've moved out a function for disabling line and feels like there were a bug in eslint-disable-next-line because it skipped errors for rules that reporting column: 0 (like max-len or valid-jsdoc, etc.).

Fixes #8781

[eslintbot]

LGTM

[mention-bot]

@zxqfox, thanks for your PR! By analyzing the history of the files in this pull request, we identified @nzakas, @tofumatt and @gyandeeps to be potential reviewers.

[not-an-aardvark]

Thanks for the PR.

Since this is a change to core, would you mind making an issue with a proposal for it? According to our guidelines, all changes to core need to have an issue so that the proposal can be discussed independently of the implementation. (Admittedly, this proposal is relatively straightforward, but I still think it would be good to make an issue for it.)

[qfox]

Ouch, missed that. Filing... → #8781

[gyandeeps]

are we still doing this? if not then we should close this.

[not-an-aardvark]

#8781 was accepted, so we are doing this change.

However, the implementation of eslint-disable comments has changed significantly since this PR was created. It looks like someone is already doing a new implementation of this PR, based on #8781 (comment).

[ilyavolodin]

Closing in favor of #9745