Closed stopfstedt closed 2 weeks ago
These are truly ugly to fix. We have a lot of them and mostly we'd just be wrapping the code in a garbage extra block. In many cases I'm not sure they're resolvable as we use multiple mixins and each breaks the other. After messing about with different options I think our best bet is to just wait for the sass release where this is changed. Looking at our code we've written it in many places expecting this to already be true. I'm not sure if that means things are going to break or be fine after the change, but I think we're better off waiting.
Fixed in frontend.
i'm seeing these in the output on application startup with this dependency update