Open shkarinn opened 3 weeks ago
Hey @shkarinn
Thanks for this detailed issue. I appreciate it. For now, the workaround will be to use comment ignores, above the tag use:
<!-- esthetic-ignore-next -->
{% img section.img %}
Optionally, you could also use:
{% # esthetic-ignore-next %}
Or wrap the tag within ignore blocks:
<!-- esthetic-ignore-start -->
{% img section.img %}
<!-- esthetic-ignore-end -->
Æsthetic logic for argument and filter formatting was overhauled and in the next release (which is almost ready for shipping) things work differently, with more rules and it will address the issue you are having. I'll also make it possible to allow singleton type tags to be included in the ignoreTagList
.
Hi, @panoply! Thank you for quick answer. Ok, I'll use the workaround for now, waiting for the next version 😊
The format.liquid.forceArgument property splits custom shortcodes in 11ty across multiple lines, which 11ty does not recognize. 11ty only processes shortcodes that are written in a single line.
When adding this tag to the ignoreTagList property, the plugin throws an error expecting a closing tag.
Steps to Reproduce:
Proposed Solution:
I'll create an 11ty issue too. But also need a workaround to exclude tags without closing.