"warning JSX not allowed in files with extension '.tsx'" about code-quality-tools HOT 4 CLOSED

As for react/prop-types I think it is best left to the user to turn the rule off. Solving for all possible permutations of rulesets x languages x project technologies could quite quickly blow on us. 💣 🔥 The easiest way to silence that rule for TS files would be to use an overrides[] stanza in .eslintrc.js and disable that rule for all .ts & .tsx files. 🤔

from code-quality-tools.

You can just specify which extensions are allowed for this rule at .eslintrc.jsonconfig file.

{
    "rules": {
        "react/jsx-filename-extension": [1, { "extensions": [".js", ".jsx", ".tsx"] }]
    }
}

from code-quality-tools.

react/prop-types is another that could be entirely turned off for typescript.

from code-quality-tools.

I'd even suggest to drop the react/jsx-filename-extension rule completely. I vaguely recall a chat with someone from Frontend team that they do not want to use react components only in .jsx files but also in .js files. What matters most is how the project is compiled and not what extension is being used.

I'll drop the rule. Flow users would hit similar problem with their .flow extensions and I bet there are other compile-to-js languages which use JSX syntax with other, exotic file extensions. 🤷‍♂️

from code-quality-tools.