Poor trigger characters for the language server
See original GitHub issueCurrently the only registered trigger character for the language server is @
:
https://github.com/graphql/graphiql/blob/65aa64811ccd40c5e8ba99edec825a91115a3c8b/packages/graphql-language-service-server/src/MessageProcessor.ts#L168
I think there are many cases when automatically triggering completions would be beneficial. For example when typing {
to select fields of an object or when typing (
after field name to specify the arguments to pass). None of those currently trigger auto-completion which means that the user has to trigger it manually with a shortcut.
Issue Analytics
- State:
- Created 2 years ago
- Comments:19 (19 by maintainers)
Top Results From Across the Web
Clarification: CompletionOptions.triggerCharacters · Issue #268
I experimented with a bunch of different IDEs and languages. In EVERY case, when you type any alphabet character, then autocomplete is ...
Read more >How to implement a multi character auto-complete trigger in ...
I'm building a language server for a custom DSL using the Pygls library. ... I've made auto-completions work with this trigger character.
Read more >Lsp - Neovim docs
Nvim supports the Language Server Protocol (LSP), which means it acts as a client ... (how it was triggered, and by which trigger...
Read more >User Manual - rust-analyzer
This manual focuses on a specific usage of the library — running it as part of a server that implements the Language Server...
Read more >ElixirLS - the Elixir Language Server - Chat / Discussions
TL;DR: I've just released an implementation of Microsoft's IDE-independent Language Server Protocol for Elixir. It adds language support and ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m a LSP client developer for ST so I “more or less” know how those things work.
additionalTextEdits
can do various edits to the document when completion is committed but my initial issue is about showing the completions in the first place since they are not shown.When mentioning
triggerCharacters
I meant those in context of thecompletionProvider.triggerCharacters
server capability and not in context of individual completion.Also:
$
- inquery($arg: String!)
, for example