Suggestion: compress_sass_output config option

[xpe]

Suggestion: compress_sass_output config option

[xpe]

I just hand-tested my potential PR (from my fork) for my personal website; works fine. If you like this, please let me know what tests you'd like to see. I can also write some docs.

[Keats]

I don't really see the point tbh, browsers can prettify it already automatically if you need.

[xpe]

@Keats I can see why you might say that, but it isn't exclusively about pretty-printing. The current default, OutputStyle::Compressed, strips out comments. This makes OutputStyle::Expanded handy sometimes for debugging.

Aside: I looked at grass today. I can tell it is a lot of work to maintain feature-parity with dart-sass. I just contributed a PR over there, adding string:split which is currently missing. I mention this to motivate that having more control over grass's config options is helpful. One of my goto strategies when things go wrong is "get more visibility". Having one tools' config buried inside another can be a barrier, and it was here in this case, which I why I made the PR.

[Keats]

I'm not planning to add configuration options for the sass compiler atm in any way

[xpe]

I'm not planning to add configuration options for the sass compiler atm in any way

I'm a bit surprised, personally. To sum up: I provided a PR. There is a benefit to at least one user. (I doubt I'm the only one.)

Not my call to make. But if it were, the rational framing would be: benefit versus cost. Does the benefit outweigh the effort of merging the PR and maintenance? In my eyes, the cost of merging the PR is very low, expected maintenance will be very low, benefit is (admittedly) small (but not zero). For example, -0.01 + -0.02 + +.1 is still positive.

[xpe]

@Keats Thanks for your work on Zola, much appreciated.

[Keats]

Thanks for the kind words!