Make branch coverage accessible via the API #1898
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eleanorjboyd
force-pushed
the
add-branch-cov-api
branch
from
735f995 to
defc4ca
Compare
|
@eleanorjboyd Sorry I haven't gotten to this. I'm pondering whether there's anything in |
|
Commit 33f12df has |
|
Hi @nedbat- super excited thank you! I blocked off time this upcoming month to implement this- so hopefully I can get it in quick! Will keep you in the loop as I implement and release! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #1888
one edit from above proposal is I exposed
branch_statsfrom theAnalysisclass as it has the (total_exits, taken_exits) which is the info needed and is already public.another note is Im not entirely sure how to test / view the changes to the
.rstfiles for https://coverage.readthedocs.io/ so any advice here would be appreciated. Thanks!