Fix occasional type errors when running tests #935
Merged
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
I have noticed that locally `yarn test` will succeed the first time, the will fail with a type error saying `toNeverResolve` is undefined. After running `yarn jest --clearCache`, tests will pass again once then fail again. This custom Jest matcher was added in #930. Seemingly the way the type was added is causing this problem. I'm not entirely sure what's going on here. Something about the way Jest is loading this file is making Jest confused about this type. I found that it works more reliably if the type is moved to a separate file in the `types` directory.
mcmire
approved these changes
Oct 12, 2022
gantunesr
pushed a commit
that referenced
this pull request
Dec 8, 2022
I have noticed that locally `yarn test` will succeed the first time, the will fail with a type error saying `toNeverResolve` is undefined. After running `yarn jest --clearCache`, tests will pass again once then fail again. This custom Jest matcher was added in #930. Seemingly the way the type was added is causing this problem. I'm not entirely sure what's going on here. Something about the way Jest is loading this file is making Jest confused about this type. I found that it works more reliably if the type is moved to a separate file in the `types` directory.
MajorLift
pushed a commit
that referenced
this pull request
Oct 11, 2023
I have noticed that locally `yarn test` will succeed the first time, the will fail with a type error saying `toNeverResolve` is undefined. After running `yarn jest --clearCache`, tests will pass again once then fail again. This custom Jest matcher was added in #930. Seemingly the way the type was added is causing this problem. I'm not entirely sure what's going on here. Something about the way Jest is loading this file is making Jest confused about this type. I found that it works more reliably if the type is moved to a separate file in the `types` directory.
MajorLift
pushed a commit
that referenced
this pull request
Oct 11, 2023
I have noticed that locally `yarn test` will succeed the first time, the will fail with a type error saying `toNeverResolve` is undefined. After running `yarn jest --clearCache`, tests will pass again once then fail again. This custom Jest matcher was added in #930. Seemingly the way the type was added is causing this problem. I'm not entirely sure what's going on here. Something about the way Jest is loading this file is making Jest confused about this type. I found that it works more reliably if the type is moved to a separate file in the `types` directory.
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.
I have noticed that locally
yarn testwill succeed the first time, the will fail with a type error sayingtoNeverResolveis undefined. After runningyarn jest --clearCache, tests will pass again once then fail again.This custom Jest matcher was added in #930. Seemingly the way the type was added is causing this problem.
I'm not entirely sure what's going on here. Something about the way Jest is loading this file is making Jest confused about this type. I found that it works more reliably if the type is moved to a separate file in the
typesdirectory.