Skip to content

Conversation

@sandersn
Copy link
Member

Fake alias resolution only applies when the import type is followed by a qualified name. Otherwise the alias is sufficiently resolved already. The previous fix over-applied.

Fixes #34926

Fake alias resolution only applies when the import type is followed by a
qualified name. Otherwise the alias is sufficiently resolved already.
@sandersn sandersn added this to the TypeScript 3.7.3 milestone Nov 12, 2019
@sandersn sandersn merged commit f334476 into master Nov 12, 2019
@sandersn sandersn deleted the fix-import-type-resolution-in-jsdoc branch November 12, 2019 20:44
@sandersn
Copy link
Member Author

@typescript-bot cherry-pick this to release-3.7

@typescript-bot
Copy link
Collaborator

Hey @sandersn, I couldn't open a PR with the cherry-pick. (You can check the log here). You may need to squash and pick this PR into release-3.7 manually.

sandersn added a commit that referenced this pull request Nov 12, 2019
Fake alias resolution only applies when the import type is followed by a
qualified name. Otherwise the alias is sufficiently resolved already.
@sandersn
Copy link
Member Author

Manually cherry-picked and merged dfe2f07 to 3.7.

@microsoft microsoft locked as resolved and limited conversation to collaborators Oct 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

JS: Maximum call stack size exceeded at getTypeFromJSDocValueReference in 3.7.2

5 participants