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
Examples of incorrect code for this rule:
<button className={`${ cond && 'bg-blue-300' }`}>Hello</button>;
This could lead to unexpected results like <button className="false"> . But currently, this code is not warned nor fixed.
<button className="false">
Their should be a rule that auto-fixes this into
<button className={classNames(cond && 'bg-blue-300')}>Hello</button>;
or maybe
<button className={classNames({ 'bg-blue-300': cond })}>Hello</button>;
The text was updated successfully, but these errors were encountered:
Candidates of the name of this rule:
no-ternary-conditions-in-template-literals
no-conditional-template-literals
Or, should this behavior a part of prefer-classnames-function ?
prefer-classnames-function
Sorry, something went wrong.
fsubal
No branches or pull requests
Examples of incorrect code for this rule:
This could lead to unexpected results like
<button className="false">
.But currently, this code is not warned nor fixed.
Their should be a rule that auto-fixes this into
or maybe
The text was updated successfully, but these errors were encountered: