Skip to content

Conversation

sandersn
Copy link
Member

Now only the immediately preceding jsdoc of a node is retrieved by getJSDoc, although it still does the correct non-local lookup for nodes like ParameterDeclaration.

This doesn't change parsing or binding, which use the per-node Node.jsdoc property directly. But it does change everything that relies on getJSDoc, which includes the checker and language service.

Fixes #32062, which contains the analysis that justifies the change.

Now only the immediately preceding jsdoc of a node is retrieved by
getJSDoc, although it still does the correct non-local lookup for nodes
like ParameterDeclaration.

This doesn't change parsing or binding, which use the per-node Node.jsdoc
property directly. But it does change everything that relies on getJSDoc,
which includes the checker and language service.

Fixes #32062, which contains the analysis that justifies the change.
@andrewbranch
Copy link
Member

I believe this also “fixes” #31492

@sandersn sandersn merged commit b46c44d into master Jul 1, 2019
@sandersn sandersn deleted the use-only-immediately-preceding-jsdoc branch July 1, 2019 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

JSDoc comments separated by white-space should not be combined
2 participants