SourcetrailDotnetIndexer icon indicating copy to clipboard operation
SourcetrailDotnetIndexer copied to clipboard

Certain nodes and edges do not show up in the code view

Open gmkado opened this issue 4 years ago • 1 comments

First off, thanks for providing the community with this, awesome stuff!

One difference I noticed between running this on my project and exploring the sourcetrail samples is that clicking on outgoing call edge (edges going to the right of the active object) do not show up in the codeview. Neither does the active object's code. Only the incoming call edges get shown.

Just wondering if this is to be expected or I'm running the indexer wrong. Thanks!

gmkado avatar Oct 30 '21 16:10 gmkado

Hi ! This is the expected behavior. As stated in the Readme under the Disclaimer section, because there is no source-code parsing involved, there is no or only very limited source-code integration available in sourcetrail.

The only source-information the indexer has, comes from the *.pdb-files (if they are found). As this info is very limited (e.g. no info about class- or method-declarations), the source for the active object cannot be shown in sourcetrail.

But maybe the indexer is also missing some detail, as the source-code for call-edges should be available, when the related *.pdb is found.

Can you share one of the example databases you mentioned ? Comparing this to a database generated by the indexer may offer a hint about what may be missing (if that is actually the case).

packdat avatar Nov 01 '21 08:11 packdat