Valuable when you have very long namespaced names like "Fully\Qualified\Class\Name\To\NamespaceFilter" and you want to see them on diagrams like "Something\Short"

With example added.

Hi, I have placed a yml in one of my projects root and I have set a relative link for the "source" and "target" configurations. However, I did not started phpda from the root of my project and I got error because of it.

I think that phpda should read relative path from the location of the config yml file. I don't know if my proposal is good enough as I'm still looking to get familiar with phpda (I don't like it that much) but I wanted to ear from you before going any further.

I hope you can help me here. :)

Hi there

For my project i need to use hhvm as it reduces the building of the model from ~30mins to ~3mins. Everything works fine most of the time. But if i a file gets parsed that starts with:

!/usr/bin/php

If

• The TagVisitor was active
• Any PhpDoc of a method contained "@" with a white space right after it.

An \InvalidArgumentException was thrown and not catched which broke the whole process of building dependencies.

The solution in this pull request tries to ignore the Exception as it is a problem of the phpDocumentor library. At the same time it logs the occurrence. This looks quite ugly if used in the command line though. Do you have any suggestions on that?

Hello, This is a great tool. Nice work. Noticed that in your composer.json you have quite strong version specs like symfony/console: 2.6.*. Haven't tried though, but think it won't work if my project is on other symfony version, 2.3, 2.5 or 2.7. Guess then I could not add your tool to my composer.json, but would have to have a separate installation for it, and that would complicate plugin maintenance. Could you consider loosening a bit on your dependencies and use ~ version spec so the tool can be added to app require-dev w/out dependency conflicts?

I'm getting this warning on an analyzer-run:

Warning	"\Some\Namespace\Here\https://www.hipchat.com/docs/apiv2/method/get_room" is 
not a valid Fqsen. on line 75 ./src/some/namespace/here/Class.php

From the referenced api-doc:

/**
 * @see https://www.hipchat.com/docs/apiv2/method/get_room
 */

Looking at https://www.phpdoc.org/docs/latest/references/phpdoc/tags/see.html, the @see tag can either take a FQSEN, or an URI, which is wrongly interpreted here.

First thanks for this lib, it's great! But would it be possible to have a PHAR file with a self-update command to use it? Installing the lib via Composer is not always possible, especially for this kind of library depending on specific version of phpdocumentor/reflection-docblock and nikic/php-parser.

Custom filter plugin, implementing NamespaceFilterInterface interface, declared in yml as namespaceFilter option and added to composer autoload. The plugin class is well loaded, but the filter method is never called.

Hey Marco, thanks for a great tool! Really well done!

I have a situation of a project with many packages (grouped by folders) that mutually depend variously. The idea is to take one namespace and to find all other namespaces depend on it (let's name this specific namespace AnalysedFoo). If run the tool by folder it shows me only outgoing connection (or at least it doesn't show incoming dependencies that are located in other folders). If I run the tool for the entire project folder it takes way too long and the result will be probably anyway too complex and unacceptable. The excludePattern doesn't seem to work here as he can only filter out AnalysedFoo and leave all the rest (excludePattern: '/AnalysedFoo/'), or if I negate the pattern (excludePattern: '/^(?!.*AnalysedFoo).*$/') all incoming dependencies are dropped off.

To make it more clear:

• MyFolder
  • MySubFolderA (contains AnalysedFoo)
  • MySubFolderB (contains namespaces depend on AnalysedFoo and on namespaces in MySubFolderC)
  • MySubFolderC (contains namespaces depend on AnalysedFoo and on namespaces in MySubFolderD)
  • MySubFolderD (contains namespaces depend on something else)

So I want to see a diagram like

 +---------------------+
 |MyFolder\MySubFolderB|--+
 +---------------------+  |
                          |
 +---------------------+  |   +------------------------+
 |MyFolder\MySubFolderC|--+-->|MySubFolderA\AnalysedFoo|
 +---------------------+      +------------------------+

and nothing more.

Do you have any ideas how to approach a solution?

Thanks in advance!

My Environment (version of the project, operating system, or hardware)

• MacOS
• Ubuntu

PHP 7.4.8 (cli) (built: Jul  9 2020 23:43:51) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
    with Zend OPcache v7.4.8, Copyright (c), by Zend Technologies

When I run this command:

composer require --dev  mamuz/php-dependency-analysis

Actual behavior:

Using version ^2.0 for mamuz/php-dependency-analysis
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: don't install mamuz/php-dependency-analysis v2.0.2
    - Conclusion: don't install roave/better-reflection 4.8.0
    - Conclusion: don't install phpdocumentor/reflection-docblock 4.3.4|install roave/better-reflection 4.8.0
    - Conclusion: don't install phpdocumentor/reflection-docblock 5.2.1
    - Conclusion: don't install roave/better-reflection 4.7.0
    - Conclusion: don't install phpdocumentor/reflection-docblock 4.3.2|install roave/better-reflection 4.7.0|install roave/better-reflection 4.8.0|install phpdocumentor/reflection-docblock 5.2.1
    - Conclusion: don't install phpdocumentor/reflection-docblock 4.3.3|install roave/better-reflection 4.7.0|install roave/better-reflection 4.8.0
    - Installation request for phpat/phpat ^0.7.3 -> satisfiable by phpat/phpat[0.7.3].
    - Conclusion: don't install phpdocumentor/reflection-docblock 5.2.0
    - mamuz/php-dependency-analysis v2.0.1 requires phpdocumentor/reflection-docblock ~4.0 -> satisfiable by phpdocumentor/reflection-docblock[4.0.0, 4.0.1, 4.1.0, 4.1.1, 4.2.0, 4.3.0, 4.3.1, 4.3.2, 4.3.3, 4.3.4].
    - mamuz/php-dependency-analysis v2.0.0 requires phpdocumentor/reflection-docblock ~4.0 -> satisfiable by phpdocumentor/reflection-docblock[4.0.0, 4.0.1, 4.1.0, 4.1.1, 4.2.0, 4.3.0, 4.3.1, 4.3.2, 4.3.3, 4.3.4].
    - Can only install one of: phpdocumentor/reflection-docblock[5.1.0, 4.0.0].
    - Can only install one of: phpdocumentor/reflection-docblock[5.1.0, 4.0.1].
    - Can only install one of: phpdocumentor/reflection-docblock[5.1.0, 4.1.0].
    - Can only install one of: phpdocumentor/reflection-docblock[5.1.0, 4.1.1].
    - Can only install one of: phpdocumentor/reflection-docblock[5.1.0, 4.2.0].
    - Can only install one of: phpdocumentor/reflection-docblock[5.1.0, 4.3.0].
    - Can only install one of: phpdocumentor/reflection-docblock[5.1.0, 4.3.1].
    - Conclusion: install roave/better-reflection 4.7.0|install roave/better-reflection 4.8.0|install phpdocumentor/reflection-docblock 5.1.0|install phpdocumentor/reflection-docblock 5.2.0|install phpdocumentor/reflection-docblock 5.2.1
    - Installation request for mamuz/php-dependency-analysis ^2.0 -> satisfiable by mamuz/php-dependency-analysis[v2.0.0, v2.0.1, v2.0.2].

Expected behavior: Package is installed.

My Environment (version of the project, operating system, or hardware)

...replace me...

My phpda.yml:

...replace me...

When I run this command:

...replace me...

Actual behavior:

...replace me...

Expected behavior:

...replace me...

Bumps guzzlehttp/guzzle from 6.3.3 to 6.5.8.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps guzzlehttp/psr7 from 1.5.2 to 1.8.5.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps codeception/codeception from 2.5.5 to 3.1.3.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

My Environment

• Windows 10
• Tested with
  • PHP 7.3 => phpda v2.0.2
  • PHP 7.2 => phpda v1.3.1
• GraphViz 2.44: (https://ci.appveyor.com/project/ellson/graphviz-pl238/builds/32032002)
• Composer installation

My phpda.yml:

mode: 'usage'
source: 'src'
filePattern: '*.php'
ignore: 'tests'
formatter: 'PhpDA\Writer\Strategy\Svg'
target: './phpda.svg'
groupLength: 1
visitor:
  - PhpDA\Parser\Visitor\TagCollector
  - PhpDA\Parser\Visitor\SuperglobalCollector
visitorOptions:
  PhpDA\Parser\Visitor\Required\DeclaredNamespaceCollector: {minDepth: 2, sliceLength: 2}
  PhpDA\Parser\Visitor\Required\MetaNamespaceCollector: {minDepth: 2, sliceLength: 2}
  PhpDA\Parser\Visitor\Required\UsedNamespaceCollector: {minDepth: 2, sliceLength: 2}
  PhpDA\Parser\Visitor\TagCollector: {minDepth: 2, sliceLength: 2}

When I run this command:

.\vendor\bin\phpda.bat analyze phpda.yml

Actual behavior:

Error:

Write dependency graph to C:\xxx\./phpda.svg
Error: C:\xxx\AppData\Local\Temp\graE965.tmp: syntax error in line 3 near '-1'

Temp file:

digraph {
  graph [rankdir="LR" ranksep=1 nodesep=0.1 fontsize=8 label="PhpDependencyAnalysis by Marco Muths (dev-master)"]
  subgraph cluster_-1 {
...

It seems that graphviz does not accept group ids like subgraph cluster_-1:

When I remove the *-1 in https://github.com/mamuz/PhpDependencyAnalysis/blob/v2.0.2/src/Layout/Helper/GroupGenerator.php#L97 everything works fine.

My Environment: Image Inspection

  "Created" : "2019-04-11T16:01:41.794400681Z",
  "DockerVersion" : "18.03.1-ee-3",
  "Id" : "sha256:93b4a875d42eaac95fbfcc1187922a70ffc4c657e47d9241c2e638a2b512c8b8",
  "Os" : "linux",
  "OsVersion" : null,
  "Parent" : "",
  "Size" : 109392129,
  "RepoTags" : [ "mamuz/phpda:latest" ],

My phpda.yml: Basically from the README.md

mode: 'usage'
source: './api'
filePattern: '*.php'
ignore: 'tests'
formatter: 'PhpDA\Writer\Strategy\Svg'
target: './phpda.svg'
groupLength: 1
visitor:
  - PhpDA\Parser\Visitor\TagCollector
  - PhpDA\Parser\Visitor\SuperglobalCollector
visitorOptions:
  PhpDA\Parser\Visitor\Required\DeclaredNamespaceCollector: {minDepth: 2, sliceLength: 2}
  PhpDA\Parser\Visitor\Required\MetaNamespaceCollector: {minDepth: 2, sliceLength: 2}
  PhpDA\Parser\Visitor\Required\UsedNamespaceCollector: {minDepth: 2, sliceLength: 2}
  PhpDA\Parser\Visitor\TagCollector: {minDepth: 2, sliceLength: 2}

When I run this command:

docker run --rm -v "%cd%":/app mamuz/phpda

Actual behavior: Output of following, with the cursor blinking at the end. Remains on that state still after an hour.

PhpDependencyAnalysis by Marco Muths v2.0.2

Configuration read from /app/phpda.yml

   0/2293 [>---------------------------]   0% < 1 sec/< 1 sec Memory: 26.0 MiB
 229/2293 [==>-------------------------]   9% 2 secs/20 secs Memory: 32.0 MiB
 458/2293 [=====>----------------------]  19% 3 secs/15 secs Memory: 34.0 MiB
 687/2293 [========>-------------------]  29% 5 secs/17 secs Memory: 36.0 MiB
 916/2293 [===========>----------------]  39% 6 secs/15 secs Memory: 36.0 MiB
1145/2293 [=============>--------------]  49% 8 secs/16 secs Memory: 44.0 MiB
1374/2293 [================>-----------]  59% 10 secs/17 secs Memory: 46.0 MiB
1603/2293 [===================>--------]  69% 12 secs/17 secs Memory: 46.0 MiB
1832/2293 [======================>-----]  79% 14 secs/18 secs Memory: 46.0 MiB
2061/2293 [=========================>--]  89% 17 secs/19 secs Memory: 46.0 MiB
2290/2293 [===========================>]  99% 19 secs/19 secs Memory: 48.0 MiB
2293/2293 [============================] 100% 19 secs/19 secs Memory: 48.0 MiB

Write dependency graph to /app/./phpda.svg

Expected behavior: svg should be generated and the console should report its progress and finally a success or detailed error message.

My Environment (version of the project, operating system, or hardware): Any environment will do. I'm using phpda 2.0.2 from composer.

My phpda.yml: Any config file, e.g. the default.

When I run this command: vendor/bin/phpda

If the project analyzed uses PSR5 array union types, e.g.

* @return (string|array)[]

You get:

Warning "\array)" is not a valid Fqsen. on line [line + file]

PSR5 array union types are already supported by TypeResolver/ReflectionDocBlock. The problem seems to be that, in order to parse the union type, TypeResolver splits the line at ( and )[] (ref). However, NameResolver strips every occurrence of [], hence TypeResolver will try to split (string|array), which in turn gives the following parts:

[ '(', 'string', '|', 'array)' ]

and the last one isn't recognised as a valid type.