We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We've noticed that slashes in the CSS output are doubling in quantity. Therefore, this:
static override styles = css` .block { content: "\\e90e"; } `;
Is becoming this:
static override styles = css` .block { content: "\\\\e90e"; } `;
I've made a reproduction of the problem here: https://github.com/adrianbruntonsagecom/postcss-lit-escaping-issue
To see it: Clone repo: git clone https://github.com/adrianbruntonsagecom/postcss-lit-escaping-issue.git
git clone https://github.com/adrianbruntonsagecom/postcss-lit-escaping-issue.git
Install dependencies: npm i
npm i
Run postcss: npm start
npm start
You'll see output.ts is generated with twice the number of slashes in the content property than expected.
The text was updated successfully, but these errors were encountered:
i suspect i've fixed this in #52 FYI
Sorry, something went wrong.
Looks like it does the job thanks :)
Successfully merging a pull request may close this issue.
We've noticed that slashes in the CSS output are doubling in quantity. Therefore, this:
Is becoming this:
I've made a reproduction of the problem here:
https://github.com/adrianbruntonsagecom/postcss-lit-escaping-issue
To see it:
Clone repo:
git clone https://github.com/adrianbruntonsagecom/postcss-lit-escaping-issue.git
Install dependencies:
npm i
Run postcss:
npm start
You'll see output.ts is generated with twice the number of slashes in the content property than expected.
The text was updated successfully, but these errors were encountered: