-
Notifications
You must be signed in to change notification settings - Fork 11
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
support autocompletion/hinting #51
Comments
i'm not sure either but i always thought we'd need an LSP for it (which we'll definitely want to do). like when the editor is trying to autocomplete a "shapes" value, i don't think it'd be able to know to pull from list of shape values for autocomplete with just openapi definitions. |
Yeah, nested structures could not be mapped with openapi alone I guess. But I guess it is not rocket science to set up a language server. Probably tedious work. |
yeup, i'll leave this open as it eventually will be vscode task, but we have one for LSP in d2: terrastruct/d2#104 |
When I have time, I'll setup a branch that has the framework for an LSP on the client side. The hard part is going to be the "error tolerant parser" on the server side :) https://code.visualstudio.com/api/language-extensions/language-server-extension-guide |
@alixander and @gavin-ts I have branches in both D2 and D2-VSCODE called LanguageServer that have a working language server. Please check them out. Have the following working:
Check it out. I'll try to work on autocomplete for styles if I can figure out what to trigger it on. |
So these would be the 2 PRs right? We can create these to review/work on |
Like the title says. I don't know how that is done best for extensions, but I've seen it done via published openapi definitions.
The text was updated successfully, but these errors were encountered: