Uh oh!
There was an error while loading. Please reload this page.
Breaking Coverage Site into Template - #43
Conversation
mhdawson
commented
Nov 28, 2016
It will probably run, but it introduces a new dependency that is not already installed by default on our CI machines. How much does using pystache simplify the generation and can it be installed through pip ? We don't have pip installed yet by default on the CI machines but I think that is going to happen, so installation through pip as part of Ansible in the future may be reasonable. |
ryanmurakami
commented
Nov 28, 2016
It is installable via pip: |
mhdawson
commented
Dec 7, 2016
I'm ok if @jbergstroem does not have any concerns. @jbergstroem can you chime in here. |
Trott
commented
Sep 28, 2017
Should this stay open? |
ryanmurakami
commented
Sep 29, 2017
@Trott I can resolve the conflicts. I think the PR is still relevant. |
Trott
commented
Mar 13, 2018
I believe coverage stuff is now in the main repo. Closing, but feel free to comment or re-open if you think I'm wrong about that. |
This PR was inspired by comments in #41. It breaks out the coverage site markup into a separate file and uses a templating engine to render it.
@mhdawson I used pystache to do the template rendering. Let me know if you see any issues with running this on the hardware.