feat: export jestSetup for mocks#116
Open
coolsoftwaretyler wants to merge 1 commit into
Open
Conversation
dominicstop
force-pushed
the
master
branch
9 times, most recently
from
53aafd1 to
e98d0b3
Compare
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
1 participant
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.
Hey folks,
I needed to set up a Jest mock for the library and found #12. I think the sample mock in that issue works pretty well, and including it in the codebase should make it easy to keep up to date.
I followed the naming scheme that react-native-gesture-handler uses (
jestSetup.js) and added it to thepackage.jsonfilesarray.I'm happy to add some docs, but not exactly sure where the best spot to put them is. Users should be able to access the mock by importing it like this:
At the top of their
jest.setup.tsfile.