This repository has been archived by the owner on Oct 23, 2023. It is now read-only.
fix: jest.mock()
is not allowed to reference any out-of-scope variables #18
#41
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 fixes two issues with mock variable names.
The variable names are derived from the imported file name instead of the imported variable name.
Current build imports
IonInput
from@ionic/react
which gets the var name as react_1 which is out of scope of the jest mock which jest will complain about.This PR uses the IonInput from the
rest
variable which is in the mock scope.The import mockUseIonPicker gets the name from the filename instead of the export variable name in the build causing it to lose the mock in front of it. This PR renames the file to include mock in it.
fixes #18