"georgejecook" wrote:
I tried your plugin; it's impressive; but unfortunately offers NO navigation at all - I can't even jump to a function defined in the same file.
for me, the ability to jump straight to a function/field definition/code behind file/other script file, is way more important than text completion.
I don't know the underlying tech unfortunately; how hard will it be to add modern code navigation?
Thanks for taking a look at it. We focused heavily on building the most accurate/complete grammar and AST possible because it's the backbone of practically every other feature we would want in the future. We then decided to cover linting capabilities because that's what my team felt would be most helpful.
Adding navigation shouldn't be too difficult there as a language server capability defined for this called a
Goto Definition Request. After registering it, you would receive a
callback with the line and location of the requested symbol whenever the user triggers this action from the IDE (via a key binding like cmd/ctrl click or some context menu). You would then parse the file using
wist, traverse the AST, then decide what potential matches are and return the one you are most confident in.
Here's a sample
implementation in the JS language server.
At the moment, i'm a bit more focused on enhancing the parser/linter performance and possibly building out a code formatter so I can't say when i'll get to this. However, community contributions to the project are very welcome
😉
