warnings used without a fallback

[Memoyr]

is it possible to deactivate this warning, "used without a fallback " ?
thanks

[Skotu]

Yes, it's annoying me a lot, so would like to have some option to deactivate it.

[peterschmiz]

As far as I could understand - based on the source code - neither strict or warnings options key has any effect on the warning :(

[archansel]

+1

[bradennapier]

+1000

I have about 180 copies of 40 variables because I need to include :root() in EVERY single css file due to this problem.

I have a root level of variables and 1000's of css files in our app that all expect to reference the variables (theme) in the globally included css file.

This completely kills the app since I either geet thousands of lines of warnings on every save or I get thousands of lines of redundant css

[s-panferov]

Please add an ability to disable the warning. In out product we use both "real" and "fake" css-properties, and this warning is annoying.

[LeaVerou]

Add me to the list of people wanting to suppress this warning. I've used warnings: false, doesn't do anything.

[LeaVerou]

If anyone wants to work on a PR, the relevant line seems to be:

postcss-custom-properties/index.js

Line 45 in 4031a44

"variable '" + name + "' is undefined and used without a fallback",

However, warnings is not defined in that scope, so it doesn't seem as trivial as just wrapping that with an if (warnings) { ... } :/

[jonathantneal]

Would #67 also work as a solution, @LeaVerou? I’ve requested permission to resolve and merge it ASAP.

[LeaVerou]

@jonathantneal the code is a bit awkward, but it should work.

[jonathantneal]

Resolved via #67, published as 6.1.0.

[SuperOl3g]

And how about to add the ability to turn this warning into error?