-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
[Bug] Configuration for rule "dot-notation" is invalid #303
Comments
I'll look into it.
…On Sat, 16 May 2020, 20:08 Muhammad Ubaid Raza, ***@***.***> wrote:
*What version of this package are you using?*
"eslint": "^7.0.0",
"eslint-config-prettier": "^6.11.0",
"eslint-config-standard": "^14.1.1",
"eslint-config-standard-with-typescript": "^17.0.0",
"eslint-plugin-import": "^2.20.2",
"eslint-plugin-jest": "^23.13.0",
"eslint-plugin-node": "^11.1.0",
"eslint-plugin-prettier": "^3.1.3",
"eslint-plugin-promise": "^4.2.1",
"eslint-plugin-standard": "^4.0.1",
*What operating system, Node.js, and npm version?*
Windows: 10, Node.js: 12.16.0, mpn: 6.14.4
*What happened?*
version 16 for eslint-config-standard-with-typescript works fine but
version 17 throws error:
Oops! Something went wrong! :(
ESLint: 7.0.0
Error: .eslintrc.json » eslint-config-standard-with-typescript » eslint-config-standard:
Configuration for rule "dot-notation" is invalid:
Value {"allowKeywords":true,"allowPattern":"","allowPrivateClassPropertyAccess":false} should NOT have additional properties.
at validateRuleOptions (D:\current\brain.js\node_modules\eslint\lib\shared\config-validator.js:132:19)
at D:\current\brain.js\node_modules\eslint\lib\shared\config-validator.js:187:9
at Array.forEach (<anonymous>)
at validateRules (D:\current\brain.js\node_modules\eslint\lib\shared\config-validator.js:184:30)
at validateConfigArray (D:\current\brain.js\node_modules\eslint\lib\shared\config-validator.js:312:9)
at CascadingConfigArrayFactory._finalizeConfigArray (D:\current\brain.js\node_modules\eslint\lib\cli-engine\cascading-config-array-factory.js:464:13)
at CascadingConfigArrayFactory.getConfigArrayForFile (D:\current\brain.js\node_modules\eslint\lib\cli-engine\cascading-config-array-factory.js:275:21)
at FileEnumerator._iterateFilesRecursive (D:\current\brain.js\node_modules\eslint\lib\cli-engine\file-enumerator.js:467:49)
at _iterateFilesRecursive.next (<anonymous>)
at FileEnumerator.iterateFiles (D:\current\brain.js\node_modules\eslint\lib\cli-engine\file-enumerator.js:287:49)
*What did you expect to happen?*
Lint the code normally.
*Are you willing to submit a pull request to fix this bug?*
I wish I could!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#303>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE3FR7D4BMIBCY3OUPXZNDRR2F6LANCNFSM4NC5HKSQ>
.
|
Could you please attach the output of |
Same problem What version of this package are you using?
What operating system, Node.js, and npm version? What happened?
Output of $ npx eslint --print-config $PATH_TO_CONFIG
What did you expect to happen? Are you willing to submit a pull request to fix this bug? Thanks |
I would like to examine this hands on. Could anyone please provide a minimal reproduction repository? |
@mightyiam Just update the version and try: https://github.com/BrainJS/brain.js/tree/git-hooks |
I have same problem
I changed eslint-config-standard-with-typescript to 16.0.0 to fix now. |
Same problem What version of this package are you using?
What operating system, Node.js, and npm version? this repository has minimal configuration: error-standard-with-typescript |
Thank you for the reproductions. Have not gotten to the bottom of this yet. |
It looks like a bug in typescript-eslint plugin. |
Strange but why does this only happens when using: |
@mubaidr because support of the new rule dot-notation has been added in that release. |
Created new issue in |
This PR should fix the issue #314 |
This seems to be our own issue. Does anyone know how to write a test that would trigger this issue and fail for it, please? Or at least provide some hint for that? |
This fixes #303 invalid configuration for dot-notation
This may help anyone looking for a solution. {
"parserOptions": {
"project": ["path/to/your/tsconfig/file"]
}
} |
What version of this package are you using?
What operating system, Node.js, and npm version?
Windows: 10, Node.js: 12.16.0, mpn: 6.14.4
What happened?
version
16
foreslint-config-standard-with-typescript
works fine but version17
throws error:What did you expect to happen?
Lint the code normally.
Are you willing to submit a pull request to fix this bug?
I wish I could!
The text was updated successfully, but these errors were encountered: