-
Notifications
You must be signed in to change notification settings - Fork 16
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
Completion: Support fields from imported files #5
Comments
I'd like to take a crack at this. I'm not too familiar with LSP nor this repo but from what I see, what needs to be done is,
If I'm too far off let me know and I'll stay away from this :) But for me having this would greatly help in navigating complex jsonnet libs! |
Progress towards #5 Logic is starting to leak out of the processing lib as I haven't found an interface that makes sense for this Some of this should probably be re-architected. However, I believe it is good enough for now and tests are in-place if we want to refactor a bit
* Completion from imports: Basic cases Progress towards #5 Logic is starting to leak out of the processing lib as I haven't found an interface that makes sense for this Some of this should probably be re-architected. However, I believe it is good enough for now and tests are in-place if we want to refactor a bit * Better structure, fix lint * Add unsupported case
This feature would be an absolute game changer for us. Is there any more news on any work towards this? |
What is the current state of completion right now with the language-server? From my experiments in Neovim and VsCode the only completion that I can get to work is from the std library. Although I did see #78, I am not sure if it adds other completion that I am missing out on at the moment. In terms of tooling, I really think full completion support is a game changer, and would help make jsonnet less daunting for new comers/ease its adoption. |
It works but only with a single level. So |
Closes #5 Simplified the code in the process. Completion was using it's own stack-walking code, I moved it to use the same thing as go-to-definition
Closes #5 Simplified the code in the process. Completion was using it's own stack-walking code, I moved it to use the same thing as go-to-definition
No description provided.
The text was updated successfully, but these errors were encountered: