coveragepy
coveragepy copied to clipboard
[xmlreport] when a filepath is in multiple source dirs, choose the highest one
fixes #578
@alex Will https://github.com/nedbat/coveragepy/issues/578#issuecomment-413881957 sill work with your update?
Maybe! I'm not sure. I'm also now many yaks deep and mostly turned my attention towards: https://github.com/nedbat/coveragepy/issues/1147
@Alex 😁 nice! Well I put another pr for the docs.
@alex Will #578 (comment) sill work with your update?
@christopherpickering Sorry for jumping in on this, but is this what is still needed to merge this PR? And if so, why is this not covered by the tests?
@gro1m I'm not sure, that was a long time ago.
@gro1m I'm not sure, that was a long time ago.
@christopherpickering I understand that, on the other hand the change is small: the source_path is traversed bottom up from the filesystem tree, i.e. deepest level first to top-level and all tests are green. From that perspective, I do not really see what holds this back and I think to avoid ambiguity it would be really great to have the whole file path and not just the filename. So it would be great if someone could tell what is needed to merge this PR...
@gro1m I'm not sure, that was a long time ago.
@christopherpickering I understand that, on the other hand the change is small: the source_path is traversed bottom up from the filesystem tree, i.e. deepest level first to top-level and all tests are green. From that perspective, I do not really see what holds this back and I think to avoid ambiguity it would be really great to have the whole file path and not just the filename. So it would be great if someone could tell what is needed to merge this PR...
Any thoughts on this @alex @nedbat ?
Is this still valid? Seems like it passed almost all checks but is a bit old
Is this still valid? Seems like it passed almost all checks but is a bit old
I think so, but I am not a contributor to the project. In the end, we could also fix the issue by using the workaround in https://github.com/nedbat/coveragepy/issues/578#issuecomment-413881957.