fix: output report generation#355
Merged
ricardogobbosouza merged 2 commits intowebpack:masterfrom May 22, 2024
Merged
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #355 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 7 7
Lines 246 247 +1
Branches 50 54 +4
=========================================
+ Hits 246 247 +1 ☔ View full report in Codecov by Sentry. |
outputReport generationoutputReport generation
outputReport generation610aea5 to
c3dba49
Compare
Collaborator
|
I added a test to cover the content of the output report |
alexander-akait
approved these changes
May 22, 2024
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
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.
This PR contains a:
Motivation / Use-Case
The changes in #300 broke the
outputReportfunctionality, specifically:means that the
contentthat is written to the output file, is always just the.toString()of theoutputReport.formatteritself. For example:I have not added additional tests for this change, as I am unable to run the existing test suite:
Please note that the existing
output-report.test.jstest cases do not assert the content of the output file at all, just that it was created. This will be why the tests did not catch this regression when it occurred.