Skip to content

Support hierarchical document outline via DocumentSymbol #174

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
Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

Support hierarchical document outline via DocumentSymbol #174

wants to merge 5 commits into from

Conversation

@ire4ever1190
Copy link

@ire4ever1190 ire4ever1190 commented Dec 10, 2023

This uses DocumentSymbol if the client supports it which allows enum/type fields to be shown

proc test() = discard

type
  Something = object
    hello*: tuple[name: string]
  Test = enum
    Colour

Produces

image

@ire4ever1190
Render type fields as fields
7b5a32d
@ire4ever1190
Add capabilities check
2c7e900 
I used a function instead of just setting flags since capabilities can have extra values assoicated with them
@ire4ever1190
Add needed types
293f6f9 
Guess enums aren't supported which is why the other enum like fields use ints

Should I write PR to add support to JSONSchema
@ire4ever1190
Implement returning DocumentSymbol[] when client supports it
63db99b
@ire4ever1190
Only show symbols for the current files
78bbc1b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@ire4ever1190