Skip to content

fix: handle string-based import names when resolving Jest functions #1761

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 13, 2025

Conversation

G-Rath
Copy link
Collaborator

@G-Rath G-Rath commented Jun 13, 2025

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

@github-actions github-actions bot added the bug label Jun 13, 2025
@G-Rath G-Rath force-pushed the support-strings-calls branch from e3e2cc5 to b1331eb Compare June 13, 2025 03:03
@G-Rath G-Rath merged commit d8b5e0e into main Jun 13, 2025
59 checks passed
@G-Rath G-Rath deleted the support-strings-calls branch June 13, 2025 04:02
github-actions bot pushed a commit that referenced this pull request Jun 13, 2025
## [28.13.5](v28.13.4...v28.13.5) (2025-06-13)

### Bug Fixes

* handle string-based import names when resolving Jest functions ([#1761](#1761)) ([d8b5e0e](d8b5e0e))
Copy link

🎉 This PR is included in version 28.13.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant