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
Hi,
I am using gulp-sass-lint as part of my build process, and have it set to output any errors or warning to a HTML report, however...
The ESLINT report seems to be generated very badly at the moment... Rather than wrapping the errors in a HTML template, it seems to be wrapping each error in the HTML template and then wrapping THAT in a HTML template, this makes the HTML report unusable, as all the JS and CSS that is brought in with the template is interfering with each other...
I can confirm it is the plugin as when you use sass-lint on it's own from the command line, it generates the reports correctly...
Please could you take a look?
The text was updated successfully, but these errors were encountered:
ghost
changed the title
EsLint report generated badly
HTML Formatter for EsLint generating unusuable report
May 18, 2017
ghost
changed the title
HTML Formatter for EsLint generating unusuable report
HTML Formatter for EsLint generating unusable report
May 18, 2017
I am seeing the same problem. It makes it so opening some of the error pages open then immediately close.
A possible related issue:
The output is also very different from what sass-lint outputs (apart from just the page template inside a page template), the output from gulp-sass-lint leaves off files that sass-lint CLI includes.
Hi,
I am using gulp-sass-lint as part of my build process, and have it set to output any errors or warning to a HTML report, however...
The ESLINT report seems to be generated very badly at the moment... Rather than wrapping the errors in a HTML template, it seems to be wrapping each error in the HTML template and then wrapping THAT in a HTML template, this makes the HTML report unusable, as all the JS and CSS that is brought in with the template is interfering with each other...
I can confirm it is the plugin as when you use sass-lint on it's own from the command line, it generates the reports correctly...
Please could you take a look?
The text was updated successfully, but these errors were encountered: