Skip to content

Fix scope of @typedef references#16718

Merged
2 commits merged into
masterfrom
findAllRefs_typedef
Jun 28, 2017
Merged

Fix scope of @typedef references#16718
2 commits merged into
masterfrom
findAllRefs_typedef

Conversation

@ghost
Copy link
Copy Markdown

@ghost ghost commented Jun 23, 2017

Previously, if a @typedef comment was attached to a function, we considered that function to be its container. Now we make sure to go to the function's parent before looking for a container.

@ghost ghost force-pushed the findAllRefs_typedef branch from 8389d53 to 4d22781 Compare June 23, 2017 19:51
@ghost ghost force-pushed the findAllRefs_typedef branch from 4d22781 to b748d19 Compare June 23, 2017 19:52
////function f2(obj) { return 0; }

const [r0, r1, r2] = test.ranges();
verify.singleReferenceGroup("type T = number");
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't used singleReferenceGroup; does it interact with the result of test.ranges somehow? I expected to see r0, r1, r2 passed in to it somehow.

Copy link
Copy Markdown
Author

@ghost ghost Jun 28, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By default it uses all ranges. The line above it is useless though.

@ghost ghost merged commit 2ccfe50 into master Jun 28, 2017
@ghost ghost deleted the findAllRefs_typedef branch June 28, 2017 20:30
@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.

2 participants