Bart Veneman

For Project Wallace's CSS Analyzer I've built a function that 'solves' this problem: - preserves (multi-line) comments - preserves correct quotes around `font: 1em/1 "Font Name", 'font_name';` - preserves multi-line...

On closer inspection I found that this is 99% reliable, minus some leading/trailing whitespace here and there: ```js function stringifyNode(node) { return css.substring(node.loc.start.offset, node.loc.end.offset) } ```

It looks like @ngtr6788 already implemented a fork for this for Svelte over here: https://github.com/sveltejs/svelte/pull/9098/files#diff-ed2fad2b231aca18fc2b692be85898d0099355fc12ceca4bdd2990faf5159d94, although it doesn't seem merged yet.

Thanks for the clarification!

Seems like a duplicate of #78 perhaps?

I posted a workaround in that one: https://github.com/csstree/csstree/issues/78#issuecomment-1368057828

> With https://github.com/w3c/csswg-drafts/issues/8970, it could make sense to do so Yes, generally I'm a proponent of making things explicit. And since your CSS would require the `&` already, why not...

Or show all unique values, like here? (personal very early side project): https://projectwallace.herokuapp.com/users/1/projects/8/metrics/unique_zindexes

That sounds reasonable, although I've seen some projects using groupings like 100-103 for site headers, 200-204 for some component and 900-910 for modals. As always, I guess: it depends

> Personally I'd like to see the highest value and the total number of unique values. > > But I’m not sure it’s parkers job to show this. So maybe...