Skip to content
This repository was archived by the owner on Sep 2, 2020. It is now read-only.

lsp: textDocument/documentSymbol support - #195

Open
stephen wants to merge 4 commits into
graphql:masterfrom
stephen:stephen/outline
Open

lsp: textDocument/documentSymbol support#195
stephen wants to merge 4 commits into
graphql:masterfrom
stephen:stephen/outline

Conversation

@stephen

@stephen stephen commented Dec 26, 2017

Copy link
Copy Markdown
Contributor

This PR adds support for textDocument/documentSymbol to the lsp-compatible server.

Here's a screenshot in vscode:
outline

@stephen

stephen commented Jan 3, 2018

Copy link
Copy Markdown
Contributor Author

@asiandrummer could you ptal at this and #196?

@asiandrummer

Copy link
Copy Markdown
Contributor

Yeah sorry - I'll review this now

Field: SymbolKind.Field,
OperationDefinition: SymbolKind.Class,
FragmentDefinition: SymbolKind.Class,
FragmentSpread: SymbolKind.Struct,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should we look to add more symbols in the future, e.g. ObjectTypeExtension and such?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Sounds reasonable to me - I haven't worked very much with the SDL, so I only implemented what the outline code already does here: https://github.com/stephen/graphql-language-service/blob/90c4c5899f3f14216794636749210386fa749427/packages/interface/src/getOutline.js#L21-L30

@asiandrummer asiandrummer left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks for implementing this - I'll cut a release with a fix I'm planning to add soon.

@lostplan

lostplan commented Feb 6, 2018

Copy link
Copy Markdown
Collaborator

This is awesome, merge pls? 🙏

@stephen

stephen commented Apr 26, 2018

Copy link
Copy Markdown
Contributor Author

@asiandrummer how can i convince y'all to take a look at this again? Happy to rebase and sort out merge conflicts if that's all it needs.

@lostplan

Copy link
Copy Markdown
Collaborator

I'm happy to take a look (next week at the soonest)

@lostplan

Copy link
Copy Markdown
Collaborator

Looks good to me. @stephen if you could rebase etc then I think it should be merged.

@nathanchapman

Copy link
Copy Markdown

Any update? This would be really nice to have. @stephen

@acao

acao commented Dec 12, 2019

Copy link
Copy Markdown
Member

well well well, time to recreate this for the new monorepo at https://github.com/graphql/graphiql!

some of this is gonna have to be re-done in TS but the server is still made with flow. can't wait to have this in monaco -> new graphiql too :D

@stephen @lostplan @nathanchapman what's the move? if i dont hear anything in ~1 week, I'll go ahead and take care of it, with full dev/review attribution of course! trying to get this merged in the next month or so, my bad for accidentally leaving this hanging after the migration, so important! and it was ready! le sigh.

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.

5 participants