Unmatched rule names of scoped plugins.

What version of ESLint are you using?

• v2.11.1

What parser (default, Babel-ESLint, etc.) are you using?

• default.

Please show your full configuration:

• I use @mysticatea/eslint-plugin-test plugin here.

{
    "plugins": [
        "@mysticatea/test"
    ],
    "rules": {
        "@mysticatea/test/test": "error"
    }
}

@mysticatea/test/test rule is:

    return {
        "Program": function(node) {
            context.report({
                node: node,
                message: "This is a test."
            })
        }
    }

What did you do? Please include the actual source code causing the issue.

• eslint test.js

What did you expect to happen?

test.js
  1:1  error  This is a test  @mysticatea/test/test

✖ 1 problem (1 error, 0 warnings)

What actually happened? Please include the actual, raw output from ESLint.

test.js
  1:1  error  Definition for rule '@mysticatea/test/test' was not found  @mysticatea/test/test

✖ 1 problem (1 error, 0 warnings)

---

I think we should support @mysticatea/test/test form’s rule specifier. Thought?

[mysticatea]

My suggestion is:

• "test/test" should pointer the test rule of eslint-plugin-test plugin.
• "@mysticatea/test/test" should pointer the test rule of @mysticatea/eslint-plugin-test plugin.

So this may be a breaking change.

[scottnonnenberg]

I use scoped plugins and the need to drop the scope for the rule name was initially confusing. It would help people new to scoped stuff to make the rule names a bit more predictable. Maybe support both for a while in ESLint 3, then 4x could require the scope name?