Parser bug

[Panthevm]

When forming a CSSDeclaration, the .getProperty is always formed in lowercase.

This error is critical when we are dealing with variables.

--A != --a

And when call .getExpressionAsCSSString, the case is respected, as a result, we lose the relationship

Reproducing an error: https://jsfiddle.net/dauhk27r/

[phax]

Quote from https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_custom_properties

Note: Custom property names are case sensitive — --my-color will be treated as a separate custom property to --My-color.

[phax]

I created a test case with your example, where I am reading and re-emitting the file. The output is

body {
  --a:red;
  background-color:var(--A);
}

so that looks good to me.
When calling expression.getAsCSSString() I also get it in the right casing.

[Panthevm]

Quote from https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_custom_properties

Note: Custom property names are case sensitive — --my-color will be treated as a separate custom property to --My-color.

I apparently did not explain the problem well.

You quoted above that variable names are case sensitive, but your reader will always format them in lower case.

And as a result, you get what you brought in the tests - not valid css, since there is no --A variable. since its parser brought it to lower case

[Panthevm]

Input:

body {
  --A:red;
  background-color:var(--A);
}

Output:

body {
  --a:red;
  background-color:var(--A);
}

var(--A) - variable --A not found

[phax]

@Panthevm thanks for the clarification - now I understand. Will keep you posted

[phax]

Found and resolved. Will be part of the 6.2.4 release.
Thanks for pointing that out!

Do you have any other issue in the pipeline or can I start building a release?

[Panthevm]

There are no other problems. Many thanks!