feat(istanbul-reports)!: lcov reports now use relative paths #168
Conversation
This file contains 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
Pull Request Test Coverage Report for Build 505
💛 - Coveralls |
j03m
approved these changes
Nov 28, 2019
bcoe
force-pushed
the
reporting-update
branch
from
f67275b
to
2fb43d0
Compare
The istanbul stuff is inches away from final, I don't expect any significant changes. Honestly at this point not sure why I labeled the releases alpha instead of beta. |
Merged
Closed
Closed
mcknasty
pushed a commit
to mcknasty/c8
that referenced
this pull request
Feb 2, 2024
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.
The next major release of
nycuses updated Istanbul APIs, we should move to them too.The feature I'm most excited about is support for relative paths in lcov reports (which is required for merging reports).
CC: @coreyfarrell, @j03m