Open cjduncana opened 8 years ago
Also experiencing this issue. Not using templating, same exact errors. Going to attempt to use AccessSniff directly to see if it changes anything.
It would appear for me that it was detecting files within my glob that it was not reporting that it tested. For instance, it reported my index.html had the issues which were really occurring in my angular templates.
YMMV but check your templates. EDIT: I meant to say check things like templates and other things nested within the structure that you're testing that may html be partials.
@cjduncana should investigate why it's not reporting the files the errors are originating in properly.
EDIT: Also note that the reports are not produced properly as well. The issue is the same there, wrong errors are placed in the wrong file.
Thanks in advance!
I think I've isolated the problem to having a resulting glob string such as "wwwroot*/.html". Changing it to "wwwroot/*/.html" gets the errors reported properly.
Oh and I think the bug is actually in AccessSniffer, not the gulp implementation.
Any chance of this error being fixed?
TL;DR
I get errors from this plugin, even though the HTML file already has these problems fixed. I use a templating engine, but I do not think it is relevant since this plugin is used once the files are converted into HTML.
Problem
I am using Nunjucks as a templating engine. These are the files that I have:
~/test/gulpfile.js
~/test/app/templates/layout.njk
~/test/app/templates/index.njk
If I run
gulp build
in~/test/
, I get the following error:As you can see from the Nunjucks templates, I have those two rules fulfilled. We can even check the output of this build process:
~/test/dist/index.html
The output of the Nunjucks render does have a
title
in itshead
tag and there is alang
attribute in thehtml
tag, but the error still appears. I do not think it has to do with Nunjucks since by the time that this plugin is used, its input is an HTML file. Do you know why this is happening?