feat(plugin-coverage): allow passing results as strings #499
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
github-actions
bot
added
📖 Project documentation
Tlacenka
force-pushed
the
coverage-paths-improvement
branch
from
2f2b5bd to
f0b5460
Compare
Tlacenka
force-pushed
the
coverage-paths-improvement
branch
from
f0b5460 to
9618c19
Compare
matejchalk
approved these changes
Feb 14, 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.
Related to #430
In this PR, I allow passing result paths as strings.
However, this approach can be only used for a single project setup atm as LCOV needs to prepend path to root in its records with relative paths.
Once another format is supported, the full potential along with globs will be unlocked. Created #498 for this.