-
Notifications
You must be signed in to change notification settings - Fork 7
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
Cannot insert import #28
Comments
Hi there! Thanks for the report @dougalg but I'm not really sure what are you referring to. Is this action menu provided with vanilla Nova? I wasn't able to find it with the shortcut you pointed out or inside Nova as a whole. Would you mind be more descriptive about the process or even better attaching some screenshost? Thanks a lot! |
Hi, @tommasongr thanks for your quick reply. I'm very new to Nova, so I'm not 100% sure 😅 I am using only the Vue and TypeScript plugins. After disabling the TS plugin, the action still appears: You can get this action menu by placing the cursor on the unimported item and then either clicking the "lightbulb" or pressing "CMD + SHIFT + A". The key is that the cursor (not mouse cursor, but the text entry cursor) must be on the unimported item's text. |
Hi there! Sorry for the delay. I took the weekend for a big update/refactor #29. Now a lot of options for configuring the Vue Language Server (VLS) are exposed. I'm not really sure what is the cause of your issue. Probably is something out of the scope of the extension. Maybe a problem of Nova or how Nova and the Vue Language Server communicates. I tried to upgrade the working version of VLS to the latest release but I've encountered some breaking issues. I need to investigate on it. Anyway I'm sorry that the problem isn't solved but maybe you can try to tweak the new preferences and see if something changes 🤷🏼♂️ I'll keep the issue open for now. Thanks |
You're doing this for free! Take as long as you want to reply, hahah 😄 Thanks for following up. Maybe if I can find some time it would be fun to delve into this a bit deeper, and see what the root cause is... time is, of course, the issue. |
Also, just to clarify, does auto-import work for you? |
ahaha Thanks! You are free to investigate as much as you want! I would love to have some help, also because most of the time I have no idea what I'm doing 😂 With the last update I basically rewritten all the Javascript implementation and add a lot of comments to explain as best as I can what is going on. If you decide to take a look that would help I hope. Anyway auto-import doesn't work for me either... Probably @yoyo930021 is the right person to ask for some insights on this |
Sorry, closed by accident ahaha |
Thanks a lot. I think you're right that it's probably a bug (or just missing feature) in Nova's language client. |
It works fine in vscode. Probably reason:
|
Thanks @yoyo930021 I'll reach out to @panicinc and see if they are aware of this issue |
Anyway @yoyo930021 I selected the DEBUG log level, but I don't see any useful prompts. This is all:
When I fire the import action nothing is logged in the console. Is that right? Another possible factor is that currently I'm using VLS v0.5.7 instead of the latest v0.7.2. I tried to upgrade but I encounted some breaking issues. This is what I get in the console when I try to run the v0.7.2:
Have any idea of what is going on? Thanks |
The log level only provides minimal information. I want this information.
I think it's a nova language client problem. https://microsoft.github.io/language-server-protocol/specifications/specification-current/#client_registerCapability |
Thanks! I'll report it |
Thanks @tommasongr and @yoyo930021 for debugging this! Adding a link to the Nova thread as well, to make it easier to cross-reference: https://devforum.nova.app/t/lsp-import-action-error/860 |
If I type some code and want to add an import for something, I can type CMD + SHIFT + A, and get the action menu including "add import for..." as expected for an unimported item. However, when I select that item, the import is not added.
I didn't see this as a known issue in the readme, sorry if it's listed somewhere and I missed it.
The text was updated successfully, but these errors were encountered: