Curlylint complains about split anchor tags introduces by Prettier about curlylint HOT 3 OPEN

Hey @bazzadp, thanks for the report. I wouldn’t be surprised if the parser was overly strict in that respect, having had to fix issues with it failing to parse self-closing SVG tags (#4), or uppercase HTML tags.

If you’re keen to look into this I think the fix would likely be to allow whitespace for all of the cases in

Looking at the potential implementation, there might be a fair bit of duplication, since parsing for all of those different types of tags is separated out.

In the meantime, it might help to set Prettier to htmlWhitespaceSensitivity: ignore. I’d also happily accept a PR to document this issue on the website (perhaps a new "Known issues" page either at the end of the "Introduction" section, or under "References").

Can I ask what language or Prettier plugin you’re using for your templates? I think I ran into this issue before but didn’t really make much of it since Prettier doesn’t support the template syntax of Jinja / Django Templates I most commonly work with.

from curlylint.

Finally spending time to look into this further, the issue is here:

This assumes the tag name on closing tags is directly followed with >. I think the fix could be as simple as:

-P.string("</").then(tag_name_parser).skip(P.string(">")) 
+P.string("</").then(tag_name_parser).skip(whitespace + P.string(">")) 

However I’m a bit hesitant to make parser changes like this until there is a better test suite in place. Any help towards this would be much appreciated!

from curlylint.

Upvote for this from me.

Is there a way to tell curly to ignore these types of errors in the meantime?

• 220:12 Parse error: expected one of '>', 'attribute', '{#', '{%', '{{' at 220:12 parse_error

from curlylint.