Skip to content
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

F12 (Go to definition) doesn't work in a contextual sense #350

Open
rossmkynch opened this issue Aug 17, 2023 · 0 comments
Open

F12 (Go to definition) doesn't work in a contextual sense #350

rossmkynch opened this issue Aug 17, 2023 · 0 comments

Comments

@rossmkynch
Copy link

Contextual "go to definition" (F12 shortcut) doesn't work for ECL. There are two main ways this manifests:

1: Files within the same folder.
ECL files within the same folder are able to reference each other directly, without need for qualifying scope. i.e. SomeFolder/File2.ecl may use SomeFolder/File1.ecl's functions directly, without the need for IMPORT SomeFolder or using SomeFolder.File1.someFunction. i.e. you can use File1.someFunction, but go to definition/F12 does not navigate to the file in VSC.

2: Nested folder imports.
You may use IMPORT SomeFolder.NestedFolder to access functionality. Calls must then be made using NestedFolder.SomeFunction. However, go to definition/F12 does not navigate to the file in VSC.

There is also the IMPORT SomeFolder AS SF, then calls using SF.function will also fail to go to definition, although this is more complex and understandable behaviour.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant