Skip to content
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

fix ctor range via textsearch & dont emit ref to class in ctor call #156

Merged
merged 1 commit into from
Apr 15, 2021

Conversation

Strum355
Copy link
Contributor

Previously, constructor calls would also emit a reference range for the identifier, pointing to the class. Additionally, the range for a constructor call included all the (type) parameters too.

This PR addresses this this by skipping scanning the identifier and by using text-search range finding.

Closes #154

Copy link
Member

@olafurpg olafurpg left a comment

Choose a reason for hiding this comment

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

LGTM 👍 That was a quick fix, one minor comment. Feel free to merge

@Strum355 Strum355 merged commit 0bbdd1e into main Apr 15, 2021
@Strum355 Strum355 deleted the nsc/constructor-call-noident branch April 15, 2021 13:25
@Strum355 Strum355 changed the title fix ctor range via textsearch & dont emit ref to class in ctro call fix ctor range via textsearch & dont emit ref to class in ctor call Jun 29, 2021
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.

Reference occurrences range over the entire constructor call
2 participants