feat: added support for nyc configuration throw environment variables #746
Conversation
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
|
|
@filipomar Could you add a test for this scenario? |
|
@jennifer-shehane sure, just feels like I am about to ask something dumb but: I attempted to follow the docs instructions, but they seem to be outdated. Are they or am I missing something? More over, I tried to find a PR akin to the change I'm trying to introduce, do you have a an example I can mirror? Or some basic set of instructions? |
|
Hey @jennifer-shehane do you have an update on this? |
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 introduces the ability to configure nyc through environment variables, requiring the maintenance of one less configuration file.
Such as:
NYC_CONFIG="{\"report-dir\":\"coverage/cypress\",\"temp-dir\":\"coverage/temp\"}" npm run your:testing:task