Configuration for rule "react/jsx-sort-props" is invalid
See original GitHub issueHello,
I just made the switch to eslint 3, but I still have an error when saving a file (I use atom and linter-eslint)
Error: /home/<package>/node_modules/eslint-config-airbnb/rules/react.js: Configuration for rule "react/jsx-sort-props" is invalid: Value "data["0"].shorthandLast" has additional properties.
Referenced from: airbnb Referenced from: /home/<package>/.eslintrc
Issue Analytics
- State:
- Created 7 years ago
- Comments:5
Top Results From Across the Web
Invalid configuration for rule "react/jsx-sort-props"
There is a bug in the linter rule's jsx-sort-props.js - although the docs reference a multiline property, said property does not exist anywhere ......
Read more >Error: "Configuration for rule "react/jsx-sort-props" is invalid ...
Okay so just tried to update some packages, including some eslint-related stuff and shock-of-shocks it broke stuff.
Read more >Eslint-plugin-react NPM
JSX -specific rules ;, react/jsx-indent-props, Enforce props indentation in JSX ; ✓, react/jsx-key, Disallow missing key props in iterators/collection literals.
Read more >eslint-plugin-react - npm
React specific linting rules for ESLint. ... your eslint config (add "plugin:react/jsx-runtime" to "extends" ) to disable the relevant rules ...
Read more >eslint/eslint - Gitter
And then you would need to install eslint-config-airbnb-base or one of their other ... "react/jsx-sort-prop-types": 0, "react/jsx-sort-props": 0, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Never mind, it seems that atom was using the same linter for some reason. Closing and reopening my session did the trick.
@ljharb
That was 100% my fault.