Feature request: visualize static and instance methods differently

[ilnytskyi]

Now all method are visualized like this

My\Package\Namespace\Class::methodCall

However with this approach it's not clear whether method is static or not, without digging into codebase. Some apps prefer using DI and composition (more instance methods usage) while other static methods (like in Laravel), some apps might mix both.

It might be helpful for reverse engineering or debugging to see if there are static methods among others. That might help to identify dependencies faster or places with increased memory consumption in long running processes.

Although in most places in the php and documentations both methods are referenced via ::

We could visualize methods like this

My\Package\Namespace\Class::methodStaticCall
My\Package\Namespace\Class->methodInstanceCall

or with prefixes or any other suitable approach

S My\Package\Namespace\Class::methodStaticCall
I My\Package\Namespace\Class::methodInstanceCall