Closed bjankord closed 5 years ago
For this, it looks like there is an option to ignore specific styles. The warnings we have so far are non-issues for us and I'd recommend add the following to our ignore list
'viewport-units', is only partially supported by IE 10,11
'css-gradients', is only partially supported by Safari 12,11.1, iOS Safari 10.0-10.2,10.3,11.0-11.2,11.3-11.4,12.0-12.1
'wordwrap', is only partially supported by IE 10,11, Edge 17
Feature Request
Description
Currently, our stylelint script logs a lot of warnings around browser compatibility of styles we're using. All of these are known and intended styles.
With the amount of warnings we see from the browser compat plugin when using stylelint, it can be easy to miss actual errors.
For example, here was build output from a recent contribution in the framework repo.
I have some concerns that people may be missing the errors, the things that will actually fail the build. There are a couple ways to resolve it. I think we could go through and disable the linter on the individual styles that are throwing warnings. Either line by line that has issues or see if we can configure the linter to not warning on use of things like word-wrap and css-gradients. The other option would be to run stylelint with a
--quite
flag so it only reports errors instead of warnings.I have some concerns with the
--quite
flag as I'm not sure if there are actually any warnings that would be helpful that we'd start to miss out on. Currently, the output of warnings we see from the browser compat plugin is not too helpful in my opinion.