fix: add outputFile to the jest cli flags #3472
Closed
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
rwaskiewicz
suggested changes
Jul 18, 2022
| @@ -66,6 +66,7 @@ export const BOOLEAN_CLI_ARGS = [ | |||
| 'notify', | |||
| 'onlyChanged', | |||
| 'onlyFailures', | |||
| 'outputFile', | |||
There was a problem hiding this comment.
This array that we're adding outputFile to is meant to be for boolean arguments only. For string arguments, we have a separate array in this file that currently contains outputFile.
In doing some research, outputFile is typed as a string in Jest and I'm not seeing it in @types/jest.
Is there a reason we need to add outputFile here?
rwaskiewicz
added
the
Awaiting Reply
ionitron-bot
bot
removed
the
Awaiting Reply
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.
Pull request checklist
Please check if your PR fulfills the following requirements:
npm run build) was run locally and any changes were pushednpm test) were run locally and passednpm run test.karma.prod) were run locally and passednpm run prettier) was run locally and passedPull request type
Please check the type of change your PR introduces:
What is the current behavior?
GitHub Issue Number: #3471
What is the new behavior?
outputFileworksDoes this introduce a breaking change?
Testing
Other information