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
> htmllint 'views/*.handlebars'
views/download.handlebars: line 3, col 7, text contains improperly escaped characters:
Where line 3 is the opening <head> tag. I think it really hates that non-HTML {{> analytics trackerId=trackerId}} bit. I was hoping there was some inline config like <!-- htmllint disable -->...<!-- htmllint enable --> which would toggle off all rules. I see there may be some preset trickery I could try, but I can't seem to get it to work locally where I ignore all rules for a few specific lines and then revert back to my original config.
The text was updated successfully, but these errors were encountered:
The line and column numbers should now be accurate; see #205. Other than that, the error message is correct, strictly speaking...
You should be able to disable all rules with <!-- htmllint preset="none" --> but this is crashing for me when I try it on your example. It works in the unit tests. There is not an easy way to revert it either, and it doesn't prevent the parser from getting in a bad state because of invalid html between that and the next comment tag.
See #155 for my discussion on how to add an option to ignore these kinds of tags. I'm closing this as a duplicate of #155, but fixing that issue somehow is my top priority for htmllint right now.
I have the following block of code, but it seems like HTMLLint really doesn't like that handlebars partials and throws an error:
And the error is:
Where line 3 is the opening
<head>
tag. I think it really hates that non-HTML{{> analytics trackerId=trackerId}}
bit. I was hoping there was some inline config like<!-- htmllint disable -->...<!-- htmllint enable -->
which would toggle off all rules. I see there may be some preset trickery I could try, but I can't seem to get it to work locally where I ignore all rules for a few specific lines and then revert back to my original config.The text was updated successfully, but these errors were encountered: