Add test for postcss-nesting support

[adam-lynch]

I had a weird issue in my codebase. While looking into it, I saw #153 (comment) and wrote a test for it. It turned out my issue was due to my PostCSS dependency being out of date.

The test fails due to whitespace;

│   expected: 'div:active:hover { a: 1; }'
│   actual: ' div:active:hover { a: 1; }'

I'm probably missing something obvious.

[ai]

The issue is just a whitespace?

Whitespace is low priority task for me, since they require ton of work and most people will not see the result (since they will run minifier later).

[adam-lynch]

There isn't an issue in this project. The test tests that postcss-nesting is supported / works with postcss-mixins. I think it's worth adding. It's almost passing, except for whitespace. I'm happy to fix the test assertion. I thought maybe you'd quickly see what I'm doing wrong. I created the test while looking into an issue with nesting+mixins which turned out to be an issue in my project only (my postcss was very out of date). I hope that's clear.

…

On Tue 29 Oct 2024, 20:45 Andrey Sitnik, ***@***.***> wrote: The issue is just a whitespace? Whitespace is low priority task for me, since they require ton of work and most people will not see the result (since they will run minifier later). — Reply to this email directly, view it on GitHub <#170 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAK4OKMJJELCAC7YKJB4A6LZ57XYHAVCNFSM6AAAAABQZ4Y3NSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBVGI4TMMRXGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ai]

Honestly, it looks like over complicating project maintenance.

I have 20+ open source project to support and a lot of practical experience taught me to add something only if there is a reason to do it.

If you have no practical reason, let’s keep it as-is.

[adam-lynch]

No problem