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
opacity: if((@errorText) or (@warning), 1, 0); doesn't set the opacity to 1 when errorText is defined as true.
opacity: if((@errorText) or (@warning), 1, 0);
Strangely, opacity: if((@errorText) or (@warning), 0, 1); actually does the behaviour that I want.
opacity: if((@errorText) or (@warning), 0, 1);
The text was updated successfully, but these errors were encountered:
fix(#22): Conditional or (#23)
658e357
* Fix conditionals * Adding support for nested conditionals * Use the value when comparing nodes * equality tests * Test greater than
🎉 This issue has been resolved in version 1.4.6 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
You can update to 1.4.6, and the following will work for you
1.4.6
opacity: if(@errorText or @warning, 1, 0);
🎉
No branches or pull requests
opacity: if((@errorText) or (@warning), 1, 0);
doesn't set the opacity to 1 when errorText is defined as true.Strangely,
opacity: if((@errorText) or (@warning), 0, 1);
actually does the behaviour that I want.The text was updated successfully, but these errors were encountered: