mvdschee
commented
5 years ago @davletbaev Thank you for your suggestions, I had it on my personal list of features I should add when I’m done rewriting the handling of accessibility errors.
So why my extension is not working when you change the file extension from .something to .html is because in the down right corner of VS code they specify which language type it is (language mode), if you change that to html it will start working, but you lose the advantages you have for the correct language mode.
Back to your feature request, there is one big problem with those HTML like languages, for example, twig it’s common to use {% include 'metadata.twig' %} to make your code more modular. For example:
<head>
{% block head %}
{% include 'metadata.twig' %}
{% endblock %}
</head>Which means the extension is unable to lint if there is a title in the <head> element because it’s not able to process those includes. Those includes I believe is the power of those languages, but they come with great challenges when you need to lint them based on the context of HTML structure.
Btw I have never used one of those HTML-like languages you describe, so if you find any more, drop a comment with ones you like in this issue and will try to add them as well :)
tylerkilburn
martindrzka
robisadev
Is your feature request related to a problem? Please describe. Plugin don't work with HTML-like languages, e.g. Nunjucks, Handlebars, etc. It doesn't work even if extension of file is .html.
Describe the solution you'd like Added the ability to select extensions in plugin settings.
Describe alternatives you've considered Default support for all html-like languages.