Skip to content
This repository was archived by the owner on Mar 7, 2019. It is now read-only.

Explicitly specify plugins in each file if used #35

Merged
merged 1 commit into from
Apr 23, 2018

Conversation

petrhanak
Copy link
Contributor

Following eslint config

{
  "extends": [
    "@strv/javascript/coding-styles/recommended",
  ],
  "parser": "babel-eslint",
}

fails with warning

Definition for rule 'import/no-useless-path-segments' was not found 
Definition for rule 'import/order' was not found

because eslint-plugin-import is missing in plugins section therefore was never imported. Plugins used in rules definition should be always imported.

@@ -14,6 +14,10 @@ module.exports = {
'./v15.js',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.v15.js should also include the react plugin...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oooh I see! 👍

Copy link
Member

@robertrossmann robertrossmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍, LGTM pending one review comment to be fixed.

@robertrossmann robertrossmann merged commit 3761cac into master Apr 23, 2018
@robertrossmann robertrossmann deleted the explicit-plugins branch April 23, 2018 12:16
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants