Any way to scan non-standard code dirs?

[devnix]

I'm trying out the tool, and right from the start it does only detect src and tests. Looking at https://github.com/rectorphp/argtyper/blob/main/src/Helpers/ProjectDirectoryFinder.php I see how it works.

Maybe a different approach like getting the files and folders from Composer would work better?

[TomasVotruba]

Sounds good 👍 care to PR?

[devnix]

Will look into it

[devnix]

Also it would be interesting to specify additional directories that will not be in composer.json, like a public folder with PHP entrypoints.

Should we think of an argument to add directories or files, additionaly to composer detection?

[devnix]

Another question @TomasVotruba: if composer.json defines files entries, I'm loading those files individually.

In my case, these are going to be files that only contains a list of require_once statements to load one file per function. Is PHPStan going to resolve those requires, or it's going to be blind unless I find a way to include all those files in any other way?

Edit: I guess this is one of the reasons why PHPStan reads its own configuration file instead of relying on composer.json. Maybe that configuration should be always explicit?

[TomasVotruba]

I think it should be as simple as passing arguments explicitly in CLI:

-vendor/bin/argtyper add-types .
+vendor/bin/argtyper add-types src tests public

[devnix]

That would result in very different behavior compared to the actual one and would conflict with the ProjectDirectoryFinder strategy. Should it guess directories if only one path is passed? What if I only want one directory to be scanned, without using any default directory or composer.json?

Since this is fully using PHPStan, wouldn't it be better to pass a phpstan.neon file? I guess that way it would help you to fine-tune even more details about your project, or even infer more precise types if you use plugins