fix(testing): add support for jest.config.js#229
Merged
Conversation
jaredpalmer
reviewed
Oct 11, 2019
jaredpalmer
requested changes
Oct 11, 2019
jaredpalmer
left a comment
Owner
There was a problem hiding this comment.
We should add the location of jest.config.js to our paths file so that we stay DRY.
This was referenced Feb 28, 2020
Collaborator
|
@allcontributors please add @Aidurber for code |
Contributor
|
I've put up a pull request to add @Aidurber! 🎉 |
Closed
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
3 participants
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.
Currently,
jest.config.jsis ignored. My fix is to try and check if there is ajest.config.js, if so then we just merge it into the jestConfig.This fixes #100 .
Issue #150 is in a similar vein to this but that needs some more work.