@thorn0 done 👍

@evilebottnawi The tests seem to be failing

@lydell nothing new in PR) keep in todo for investigation

@lydell @thorn0 trimEnd doesn't supported in node@4 what tips will be to insert a polyfill?

If it's an urgent fix, you can simply use .replace(/\s+$/, "") instead. Otherwise, target the 2.0.

Let's do it for next, it is not high priority

Ready for review.

(update - this is SOLVED) Known issue: quotes are stripped from inline comments in values. Difficult to fix because value-* nodes don't have correct location data, only relative to the beginning of the value. I wish postcss-values-parser had an option to pass the initial line and column.,,

Prettier pr-7021
Playground link

--parser less

Input:

a {
    opacity: // "!"
      1;
}

Output:

a {
  opacity: //  !
    1;
}

@thorn0 sounds good, let's open a issue after merge

Would it be possible to replace quotes in comments with some placeholder and then replace back to quotes at the end?

This placeholder has to be one character long. E.g. we could use \0 for single quotes. But what about double quotes? \uffff?

Yeah, why not. I think it’s more likely that people put quotes in their comments than \0 or \uffff in their CSS.