-
Notifications
You must be signed in to change notification settings - Fork 39
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
"Go to definition" support for absolute paths #121
Comments
@jackson-dean you need to get
Most relevant
|
@lifeart Thank you for working and making available I think All my JS modules are imported with the application name as the namespace root name. import myModule from 'li/utils/my-module'; If I am not wrong, that is or was an Ember requirement. Making this feature available will allow navigating easily across all the app JS modules. |
@ppcano it's definetly possible, all we need is - write kinda resolution logic for it. 1.) for absolute paths if you have time for it, you can add resolution logic to
|
@ppcano go-to definition for absolute imports commited to branch, could you test it? |
@lifeart I have tried but it does not look to be working. I think I am using correctly your branch.
Language server is working because component and helper autocompletion on handlebars works. Please, let me know if I should try something else. Note: I think the above instructions or another description explaining how to run locally the project may be useful to add on the Readme or Contribution section. |
For the js side of the resolution I discovered it can be done pretty easily using a proper jsconfig.json which uses the ts/js language server packaged with VSCode. Resolving namespaced component invocations would be very valuable though. |
@jackson-dean it's should work in |
…r-tooling#123) * fix: cursor loop * multiline + non serializable cursor tests
Using vscode, it seems "go to definition" only works for relative paths in .js files when executing it with the cursor over an import path string. It also seems there is no support yet for namespaced components which use the "::" syntax. Is there any plan to support namespaced/absolute paths in these scenarios? I would be very interested in helping add this support though i might need some guidance getting up to speed on how to run and debug the server from vscode. thanks!
The text was updated successfully, but these errors were encountered: