Problem:
I have worked on a few projects that use slather in the last few years. I have always accepted that the HTML report viewing experience will be sub-par because there are no CSS and JS files once the report (index.html) is deployed to Azure DevOps or Bitrise (I'm sure others have similar limitations).
I suggest that instead of referencing the local logo.jpg, list.min.js, highlight.pack.js and slather.css that is on disk, the HTML template should instead reference a Web/CDN version (perhaps hosted here on GitHub). This way HTML reports will be feature-rich when deployed to these services as artifacts.
Perhaps this can be opt-in eg slather coverage --html --cdn-assets
Problem: I have worked on a few projects that use slather in the last few years. I have always accepted that the HTML report viewing experience will be sub-par because there are no CSS and JS files once the report (index.html) is deployed to Azure DevOps or Bitrise (I'm sure others have similar limitations).
I suggest that instead of referencing the local
logo.jpg
,list.min.js
,highlight.pack.js
andslather.css
that is on disk, the HTML template should instead reference a Web/CDN version (perhaps hosted here on GitHub). This way HTML reports will be feature-rich when deployed to these services as artifacts.Perhaps this can be opt-in eg
slather coverage --html --cdn-assets