You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One can provide project specific composer packages within local_packages.
We now have packages following that structure and want to use class:move feature, which fails with:
[RuntimeException]
There are no class name candidates
The Phpactor\ClassFileConverter\Adapter\Composer\Psr4NameInflector will not work as it will receive /vendor/prefix/name/Classes instead of the local_packages/package/Classes path.
Adding a realpath() call within class-to-file/lib/Adapter/Composer/ComposerFileToClass seems to help. I'm not sure if that might break other things.