disabling react/jsx-no-literals does not work in files
See original GitHub issueExpected behaviour
Adding /* eslint-disable react/jsx-no-literals */
to the top of the file should disable the rule for the file in question.
Actual behavior The rule still gets triggered when running gulp-eslint.
More information Other rules (eslint default rules, or from this plugin) can be disabled just fine. Only trying to disable this specific rule does not work.
This behaviour started today – last friday everything was still fine. Gulp-eslint has not been updated since.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
disabling react/jsx-no-literals does not work in files #1440
Expected behaviour. Adding /* eslint-disable react/jsx-no-literals */ to the top of the file should disable the rule for the file in question.
Read more >ESLint rule forbidding Object Literals in JSX - reactjs
Based on my quick look at https://github.com/yannickcr/eslint-plugin-react, I could not find any rule related to this issue. I think it's a good ...
Read more >JSX In Depth
The first part of a JSX tag determines the type of the React element. Capitalized types indicate that the JSX tag is referring...
Read more >React Native development tools - Part 1: Linting tools
This is part one of a three part tutorial series examining development tools for React Native. In this part, learn how to configure...
Read more >no-throw-literal - ESLint - Pluggable JavaScript Linter
It is considered good practice to only throw the Error object itself or an object using the Error object as base objects for...
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 Free
Top 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
Problem was with the last release of eslint itself. Pinning eslint down to v4.6.1 resolves the issue for now.
I’m closing this and opening an issue with eslint.
yep, I’m going to add to that 👍