Hello @jacobstr, all feature requests are more than welcome so there is nothing to forgive.

The biggest problem with generating a callgraph is that phpDocumentor does not collect usage data (except when an @uses tag is used). This is partly because phpDocumentor collects static data and does not execute your application, hence missing dynamic calls.

Nonetheless I think your suggestion is interesting and worth researching if we can implement such a thing. However due to other running issues it might take a long time to implement it.

mvriel - I was thinking about this and wondering how Doxygen was even doing it. It runs incredibly fast so I feel it must be doing static analysis as well.

How far does phpdocumentor go? Does it for example, generate an AST of the source code of each file or does it only parse annotations?

PhpDocumentor generates a complete AST but it is currently limited to the static aspect of a project. This means that we currently do not have a callgraph available.

The data source that we use would probably make it possible to generate a callgraph (I'd have to review it to be sure) but I expect that it would require a non trivial amount of time.

This means I will keep this feature request open because I do see value in it but other issues have precedence and I do not expect this to be implemented in the short run.

@mvriel Care to point me to this data source?

Sure! We use our own library phpDocumentor/Reflection, which on turn uses the parser nikic/PHP-Parser to interpret the information returned by php. It is this latter project that I'd have to check if it exposes the internals of functions and methods