New rule: eslint-disable-next-line ...

Premise

With the // eslint-disable-line ... comment, lines can get a bit long. It’d be nice to be able to put the comment on the preceding line.

When does this rule warn? Please describe and show example code:

For example:

// eslint-disable-line no-extend-native
Map.prototype.updateGrid = function updateGrid(col, row) { 
  return this.merge({ col, row });
};

Instead of:

Map.prototype.updateGrid = function updateGrid(col, row) { // eslint-disable-line no-extend-native
  return this.merge({ col, row });
};

It’d be great if the parser was smart enough to recognize when the line is effectively blank, it’s referring to the next line. However, in case that’s unreasonable, let me propose a new rule: // eslint-disable-next-line ...

For example:

// eslint-disable-next-line no-extend-native
Map.prototype.updateGrid = function updateGrid(col, row) { 
  return this.merge({ col, row });
};

Is this rule preventing an error or is it stylistic?

Stylistic.

Why is this rule a candidate for inclusion instead of creating a custom rule?

Not sure if it can be written as a stand-alone rule.

Are you willing to create the rule yourself?

No. I’m not sure this is in my skill set.

[BYK]

@ilyavolodin I think the reason is /*eslint-disable */ requires a matching /*eslint-enable */ afterwards and doing that only for a single line, just because the line gets too long with the // eslint-disable-line directive is a bit wasteful. At least that’s how I feel and why I’d support something like this.

@bionikspoon is that accurate?

[platinumazure]

For what it’s worth, I would support this too.