Feature proposal: use CDN for assets or put them inline

[agate]

Hi,

First of all, thanks for providing such good lib!

We are using a CI tool that only takes one html as report. Which doesn't include the assets dir. I am think if we can move our images / stylesheets / javascripts to a CDN. Or just put all of them in the bottom of the html page. So the coverage folder will only have one html page (index.html).

Thanks,
Hao

[beporter]

This would help with Gitlab CI as well. You either can specify a single file which gives you a convenient link in your merge requests, or a folder, which means you have to click an extra 3-4 times to open the coverage report's index.html. If the assets were inline, the experience would be much quicker/nicer.

Edit: docs link: https://docs.gitlab.com/ee/ci/yaml/#artifactsexpose_as

[Aethelflaed]

I'm interested in that as well. I'll give it a try when I can get some time for it.

The way I see it, the CDN will be an extra configuration key, so the hosting responsibility will be on the user

[Aethelflaed]

On second thought, the assets are ~0.5m compared to the 16m index.html (on my project), and I discovered SIMPLECOV_INLINE_ASSETS which just packs everything together in a single html file, so no need for a CDN IMHO