ΝΙΚΟΛΑΣ

I had some delays because of my day time job. It's mostly ready for beta release and I am testing everything, little hesitant to drop the beta. Some last minute...

So currently, [PrettyDiff](https://github.com/prettydiff/prettydiff) handles this rule but internally it's parser ([sparser](https://github.com/unibeautify/sparser)) has some trouble with Liquid comments. Providing support for this would require taking control of comment formatting away from...

🚢 Shipped [v3.0.0](https://github.com/panoply/vscode-liquid/releases/tag/v3.0.0)

Hey @Jordakoes, This is being caused because vscode is validating the `` tag and does not understand Liquid, you can disable validation on scripts and styles if you are infusing...

🚢 Shipped [v3.0.0](https://github.com/panoply/vscode-liquid/releases/tag/v3.0.0)

Hey guys, this should be fixed in [v3.0.0](https://github.com/panoply/vscode-liquid/releases/tag/v3.0.0). Take a look at the new [readme](https://github.com/panoply/vscode-liquid) and open a new issue if you are still having trouble.

Hey @aes421 – This version leverages Grammar injections which causes this issue. This has been addressed in the next release.

🚢 Shipped [v3.0.0](https://github.com/panoply/vscode-liquid/releases/tag/v3.0.0) Grammar injections are no longer applied in HTML. The language is now recognized as Liquid.

Hey guys, For now this is the best solution to avoid such errors, it's difficult to find a fluent solution to overcome such an issue as JavaScript infused with Liquid...

Would be nice to see this become available.