exporting global expect constant #58
Open
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
otherwise in some editors (in my case vim tsserver LSP), the global type is still native jest type, and so additional parameters are not honored by exporting expect constant, that makes it explicit that global expect is overwritten
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.
otherwise in some editors (in my case vim tsserver LSP), the global type is still native jest type, and so additional parameters are not honored
by exporting expect constant, that makes it explicit that global expect is overwritten
What
exporting global
expectconstant for typescript supportWhy
Some LSP servers do not pickup updated
expectglobal and so complain that additional parameters are not supportedNotes
Housekeeping
Unit testsDocumentation is up to dateNo additional lint warnings