We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Thanks for the amazing plugin!
I have a use case, one that made us look into having a rule like this. That doesn't seem to be caught yet.
const profile: $Profile | undefined ... <div> {profile?.viewCount && <h2>Hey</h2>} </div>
The text was updated successfully, but these errors were encountered:
For reference here is a test which should throw an error:
{ code: [ 'const first = { foo: 0 };', "<App>{first?.foo && <Foo/>}</App>", ].join("\n"), errors: [{ messageId: "conditionErrorFalseyString" }], parserOptions: { ecmaFeatures: { jsx: true, }, }, output: [ 'const first = { foo: 0 };', "<App>{!!first?.foo && <Foo/>}</App>", ].join("\n"), filename: "react.tsx", },
Sorry, something went wrong.
Thanks for reporting. This should be fixed in the latest release, 1.3.1, which has just been published.
Successfully merging a pull request may close this issue.
Thanks for the amazing plugin!
I have a use case, one that made us look into having a rule like this. That doesn't seem to be caught yet.
The text was updated successfully, but these errors were encountered: