Rule IDs are magic numbers

I think the rule IDs are pretty cryptic:

{
  "comma-dangle": [2, "never"],
  "no-console": 0,
  "curly": [1, "multi-line"]
}

What about we use some mnemonic strings instead?

{
  "comma-dangle": ["require", "never"],
  "no-console": "ignore",
  "curly": ["favor", "multi-line"]
}

Where require generates errors, favor generates warnings, and ignore turns the rule off.

[lo1tuma]

I agree that those magic numbers are a bad thing, especially for a code quality tool.

I’m not sure that your proposal really improves something because the enums aren’t very meaningful without context.

I would prefer something like this:

any-rule: { severity: "error",  options: []} 
any-rule: { severity: "warning", options: []} 
any-rule: { severity: "off", options: []} 

any-rule: "error" 
any-rule: "warning" 
any-rule: "off" 

[nzakas]

I don’t want two ways of doing configuration, that increases complexity for very little gain.

@lo1tuma if you want to think about some incremental improvements for 2.0.0, add that to the wish list.

For now, we aren’t going to make any changes. The documentation is pretty clear about these numbers, we should keep pointing people to it.