fix(css_formatter): fix CSS nesting whitespace after & trimmed #3061

[denbezrukov]

Summary

Close #3061

The problem arose from using the wrong lexer context after processing the '&' token.

Test Plan

cargo test

[github-actions]

Parser conformance results on

js/262

Test result	main count	This PR count	Difference
Total	50793	50793	0
Passed	49686	49686	0
Failed	1107	1107	0
Panics	0	0	0
Coverage	97.82%	97.82%	0.00%

jsx/babel

Test result	main count	This PR count	Difference
Total	40	40	0
Passed	37	37	0
Failed	3	3	0
Panics	0	0	0
Coverage	92.50%	92.50%	0.00%

symbols/microsoft

Test result	main count	This PR count	Difference
Total	6534	6534	0
Passed	2087	2087	0
Failed	4447	4447	0
Panics	0	0	0
Coverage	31.94%	31.94%	0.00%

ts/babel

Test result	main count	This PR count	Difference
Total	667	667	0
Passed	595	595	0
Failed	72	72	0
Panics	0	0	0
Coverage	89.21%	89.21%	0.00%

ts/microsoft

Test result	main count	This PR count	Difference
Total	18217	18217	0
Passed	13961	13961	0
Failed	4256	4256	0
Panics	0	0	0
Coverage	76.64%	76.64%	0.00%

[codspeed-hq]

CodSpeed Performance Report

Merging #3082 will not alter performance

_{Comparing fix/nesting (acc93c2) with main (eb8de09)}

Summary

✅ 92 untouched benchmarks

[ah-yu]

Should we add extra space after the nesting selector if it has trailing comments? It seems Prettier doesn't handle the case very well 😅 playground link

[denbezrukov]

Should we add extra space after the nesting selector if it has trailing comments? It seems Prettier doesn't handle the case very well 😅 playground link

Interesting, thank you for that case! Actually, I don't know; it seems that the parser returns an unknown selector if there is a comment between & and .child.

[denbezrukov]

Ive converted it to draft because after @ah-yu comment I think that it's a parser issue🙈

[ematipico]

Great fix @denbezrukov! Thank you ❤️