Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validation failed for some of the rules with ESLint 7.x #294

Closed
ghaiklor opened this issue May 9, 2020 · 2 comments
Closed

Validation failed for some of the rules with ESLint 7.x #294

ghaiklor opened this issue May 9, 2020 · 2 comments

Comments

@ghaiklor
Copy link

ghaiklor commented May 9, 2020

What version of this package are you using?

14.1.1

What operating system, Node.js, and npm version?

MacOS, Node.js v14, npm v6

What happened?

According to release notes for ESLint they have more strict validation now. Getting this error with the latest ESLint version:

Error: .eslintrc.json » ../../.eslintrc.json » eslint-config-standard-with-typescript#overrides[0]:
        Configuration for rule "@typescript-eslint/indent" is invalid:
        Value {"SwitchCase":1,"VariableDeclarator":1,"outerIIFEBody":1,"MemberExpression":1,"FunctionDeclaration":{"parameters":1,"body":1},"FunctionExpression":{"parameters":1,"body":1},"CallExpression":{"arguments":1},"ArrayExpression":1,"ObjectExpression":1,"ImportDeclaration":1,"flatTernaryExpressions":false,"ignoreComments":false,"ignoredNodes":["TemplateLiteral *"],"offsetTernaryExpressions":false} should NOT have additional properties.

What did you expect to happen?

Working rules

Are you willing to submit a pull request to fix this bug?

Yes

@ghaiklor
Copy link
Author

ghaiklor commented May 9, 2020

Hmm... not sure, but after a quick investigation it looks like an issue more into typescript-eslint side, especially to the rule - https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/src/rules/indent.ts

@mightyiam mightyiam transferred this issue from standard/eslint-config-standard May 9, 2020
@mightyiam
Copy link
Owner

Most likely fixed in #299.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants