Fixed 'Flutter Coverage' extension compatibility #1
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
|
This is a good PR if it makes the coverage extension. It is even better if the coverage report is relative to the root rather than the absolute file path. The current output is not portable across file system locations. |
|
@PatrickWulfe, thanks for the contribution and credit to @freemansoft for bumping this... clearly not paying enough attention to this repo! I'll review this tonight. |
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 'Flutter Coverage' extension wasn't compatible with the coverage files being output previously. This merge aims to fix that, along with issues caused by using './' as the repo directory argument.