Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature proposal: use CDN for assets or put them inline #111

Open
agate opened this issue Jul 20, 2021 · 1 comment
Open

Feature proposal: use CDN for assets or put them inline #111

agate opened this issue Jul 20, 2021 · 1 comment

Comments

@agate
Copy link

agate commented Jul 20, 2021

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
Copy link

beporter commented Sep 28, 2021

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants