Skip to content

In TypeScript code, never bind JSDoc normally, just set parent pointers #16555

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
1 commit merged into from
Jun 15, 2017

Conversation

ghost
Copy link

@ghost ghost commented Jun 15, 2017

Fixes #16554

The fixes to #14752 (#14997) #16358 (#16413), and #16359 (#16416) were overly complex and specialized.
The only reason we needed to bind JSDoc in TypeScript code was to set parent pointers. This adds a function to do only that. (I started binding JSDoc in #15856 and should have just done this PR in the first place.)
Since we will now never reach a JSDoc node in the normal binder in TypeScript code, we can remove a bunch of checks for isInJavaScriptFile (undoing the previous specialized fixes to the above issues).

@ghost ghost force-pushed the bind-jsdoc branch from 11b1d1e to 61eb78b Compare June 15, 2017 15:17
@ghost ghost requested a review from rbuckton June 15, 2017 15:17
@mhegazy
Copy link
Contributor

mhegazy commented Jun 15, 2017

please port this to release-2.4

@ghost ghost merged commit 537695c into master Jun 15, 2017
@ghost ghost deleted the bind-jsdoc branch June 15, 2017 17:02
ghost pushed a commit that referenced this pull request Jun 15, 2017
ghost pushed a commit that referenced this pull request Jun 17, 2017
@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
This pull request was closed.
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.

Erroneous function type in @type takes effect in TypeScript code
2 participants