-
-
Notifications
You must be signed in to change notification settings - Fork 929
New issue
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
Fix false positives for interpolation in function-no-unknown #5913
Comments
@m4thieulavoie Thanks for the report and for using the template. This issue seems to be the same problem as: |
Indeed! Hopefully |
Stylelint should not handle non-standard CSS syntaxes. Instead, the For example, sanitizing a value like |
@m4thieulavoie Thanks for opening the issue.
Yes, it is.
That's correct. As @ybiquitous is implying, we ignore non-standard syntax in the built-in rules (using the |
Thanks for the feedback! I'll keep my eyes opened for a fix in |
Error: - Unexpected unknown function "mix" function-no-unknown stylelint-scss/stylelint-scss#589 (comment) stylelint-scss/stylelint-scss#589 (comment) Solution: - Disable the rule 'function-no-unknown' or add exceptions using 'ignoreFunction' stylelint/stylelint#5913
Error: - Unexpected unknown function "mix" function-no-unknown stylelint-scss/stylelint-scss#589 (comment) stylelint-scss/stylelint-scss#589 (comment) Solution: - Disable the rule 'function-no-unknown' or add exceptions using 'ignoreFunction' stylelint/stylelint#5913
- https://taroify.github.io/taroify.com/quickstart - stylelint/stylelint#5913 - `No matching export in ...` `import { createVanIconComponent } from "./van"`
What steps are needed to reproduce the bug?
When having something like the following,
stylelint
'sfunction-no-unknown
throws a false error (assumingdarken
is inignoreFunctions
What Stylelint configuration is needed to reproduce the bug?
How did you run Stylelint?
npx stylelint
Which version of Stylelint are you using?
14.5.0
What did you expect to happen?
No violation thrown by stylelint
What actually happened?
Does the bug relate to non-standard syntax?
No response
Proposal to fix the bug
Add logic to remove any
#{}
syntaxThe text was updated successfully, but these errors were encountered: