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
function-calc-no-invalid was removed and replacement is non-existent or undocumented #5713
Comments
@romainmenke Thank you for using a template! As far as I know, there seem to be no replacements. 😞 We have discussed performance and browser support for a long time (see #2454 and #3935). |
This was the main reason for its removal. It had a security vulnerability.
As @ybiquitous said, there is no replacement. Stylelint may, in the future, offer more validation if we migrate some rules to a different parser. I'm going to close the issue as the migration guide says to remove the rule from your config and that's all we can suggest at the moment. |
Refs: stylelint/stylelint#5713 Signed-off-by: vitebo <andre.vitebo@quero.com>
What steps are needed to reproduce the bug?
Have a stylelint config with
function-calc-no-invalid
in it.What Stylelint configuration is needed to reproduce the bug?
How did you run Stylelint?
Any method
Which version of Stylelint are you using?
^14
What did you expect to happen?
No errors or documentation on where to find a replacement
What actually happened?
Unknown rule function-calc-no-invalid function-calc-no-invalid
Does the bug relate to non-standard syntax?
No
Proposal to fix the bug
Write migration/deprecation docs.
This issue discusses moving it to a separate plugin : #4731 (comment)
But I can't find it anywhere.
The PR specifically mentions not doing any kind of deprecation cycle : #5296 (comment)
This issue just mentions updating a standards config :
#5653
But it does not explain why this would help or any hint of a replacement.
Can this be rectified?
I understand that some people had strong feelings about removing this rule but guiding the community is important here.
Open questions I have?
The text was updated successfully, but these errors were encountered: