Can't "go to declaration" on module name

[nazriel]

Hello.

Currently it is not possible to ctrl+click module name in the import list and go to actual source file.
DCD complains in the background that:

2017-02-28T23:57:13.740:autocomplete.d:findDeclaration:135 Could not find symbol declaration

What is more interesting is the fact, that if you use fully qualified symbol name (for example std.stdio.writeln) and click on the module name (stdio in this example) it will properly open stdio.d file without any complains from DCD.

Is it possible that VC is setting wrong Symbol Type when lookup is done in import list?

[LaurentTreguier]

This is purely a DCD problem. All the extension does is pointing DCD to a character position in the file and asking for the declaration. However, I just tested the latest DCD alpha version available with dub and this bug seems to have been fixed.
Can you try to fetch the latest alpha with dub fetch dcd --version=0.9.0-alpha6 and see if it works for you as well ? After manually fetching it, simply reload the window the extension should use it automatically.

[nazriel]

@LaurentTreguier you are right!

I've brew install dcd --devel and it works with version you mentioned.

Although I have other minor problem.
If I don't manually start DCD-Server in terminal, VC will endlessly try to restart DCD

Do you have an idea why is it happening?
Is it possible to somehow enable Debug mode for the extension?

[LaurentTreguier]

The extension only restarts the DCD server whenever a dcd-client exits with an status different from 0, which only happens upon errors.
Are you able to manually launch a successful dcd-client process after starting the server ?
As for debugging, the only way to do something like that would probably be to clone this repository and build the extension...