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.

Sign up for GitHub

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

Jump to bottom

Support symbol indexing/navigation #107

Closed
paultyng opened this issue May 21, 2020 · 2 comments
Closed

Support symbol indexing/navigation #107

paultyng opened this issue May 21, 2020 · 2 comments
Labels
enhancement New feature or request workspace

Comments

@paultyng
Copy link
Contributor

https://microsoft.github.io/language-server-protocol/specification#workspace_symbol
@paultyng paultyng added the enhancement New feature or request label May 21, 2020
@paultyng paultyng changed the title Support symbol navigation Support symbol indexing/navigation May 21, 2020
@paultyng paultyng added this to the v0.5.0 milestone May 21, 2020
@paultyng paultyng removed this from the v0.5.0 milestone Jun 10, 2020
@appilon appilon mentioned this issue Aug 27, 2020
Merged
@radeksimko
Copy link
Member

Basic block symbol navigation was done in #265 and I believe the only bit remaining here is support of nested symbols, which is tracked under #290

I'm therefore going to close this one.

@ghost
Copy link

ghost commented Dec 12, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the context necessary to investigate further.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement New feature or request workspace
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@radeksimko @paultyng