fix: handle string-based import names when resolving Jest functions #1761
+56
−2
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.
While there's no reason to actually do this for our identifiers, official support for this was added in
@typescript-eslint/parser
v8 meaning we need to handle this somehow, so this just preserves it 🤷Relates to #1756 and #1757 - the actual logic will be improved once we're using
@typescript-eslint
v8 since then the types will actually exist