How to be able to specify hover states using postcss-nested. The ability to do so was removed in PR https://github.com/andreypopp/styling/pull/10, as the syntax to do so was somewhat custom to Styling. The PostCSS Nested syntax is, of course, also non-standard, but widely used in other pre-processors.
That adding additional PostCSS plugins works, but that it is an additional step in the pipeline.
This works well for our usecase, but I'd be interested in your vision for Styling with regards to how many things it should do. For example:
Should Styling use the nesting plugin by default?
Should Styling be able to use PostCSS plugins specified with the postcss: {} key in the Webpack config without having to specify PostCSS as an additional loader? This would be more efficient, but maybe not as discoverable and a bit surprising.
I'd be happy to adjust this PR with your feedback. Thanks!
This PR shows two things:
hoverstates usingpostcss-nested. The ability to do so was removed in PR https://github.com/andreypopp/styling/pull/10, as the syntax to do so was somewhat custom to Styling. The PostCSS Nested syntax is, of course, also non-standard, but widely used in other pre-processors.This works well for our usecase, but I'd be interested in your vision for Styling with regards to how many things it should do. For example:
postcss: {}key in the Webpack config without having to specify PostCSS as an additional loader? This would be more efficient, but maybe not as discoverable and a bit surprising.I'd be happy to adjust this PR with your feedback. Thanks!