Inline comment option to warn instead of disable

The version of ESLint you are using. 6.8.0

The problem you want to solve. I have reviewed an eslint error and decided it should be a warning. Currently I do not see a way to override a line to set it to warning at the line level. It looks like currently the only options are either 1) override at the config level / file level, or 2) disable the rule completely on the line using // eslint-disable-line [rule]

Your take on the correct solution to problem. Add inline comment options for // eslint-warn [rule], // eslint-warn-line [rule], // eslint-warn-next-line [rule]

Are you willing to submit a pull request to implement this change? Potentially. Doesn’t seem too difficult if most of the code for eslint-disable can be leveraged.

[kaicataldo]

I’m not sure I understand why you would want to do this - can you explain what problem this solves? We would also need to think about the API, because the relationship between eslint-enable and eslint-warn is not very clear. Also, if someone wanted to enable both rules as errors and rules as warnings, do they have to use two different types of directive comments?

Agreed that this should go through the RFC process, but it’s also fine to get some initial feedback here.

[anikethsaha]

I think this needs a RFC as it belongs to the core 🤔