You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Add line comment command, or similar, creates <!-- foo --> within .liquid files.
It might be preferable for it to create {% comment %} foo {% endcomment %} instead, if possible?
The benefit being that the liquid compiler will strip these out, so it is the best way to add comments to liquid files, typically
The text was updated successfully, but these errors were encountered:
So currently, PrettyDiff handles this rule but internally it's parser (sparser) has some trouble with Liquid comments. Providing support for this would require taking control of comment formatting away from Sparser and creating an internal solution which I agree would be worth applying.
The
Add line comment
command, or similar, creates<!-- foo -->
within .liquid files.It might be preferable for it to create
{% comment %} foo {% endcomment %}
instead, if possible?The benefit being that the liquid compiler will strip these out, so it is the best way to add comments to liquid files, typically
The text was updated successfully, but these errors were encountered: