Compatibility with `Composer\InstalledVersions` API about composer-bin-plugin HOT 4 CLOSED

it will report packages from the main project's directory composer.json, instead of bin's.

Isn't it a problem of the binary tool picking up the wrong composer.json or autoload file? (in which case often you can reconfigure them)

from composer-bin-plugin.

The binary tool in question does not "pick up" the composer.json on its own, it just uses (through a library, but nevertheless) the API Composer provides. IMO there should be a way for the bin plugin to report to the Composer itself which composer.json is the correct one, so Composer's InstalledVersions API reports packages correctly.

from composer-bin-plugin.

IMO there should be a way for the bin plugin to report to the Composer itself which composer.json is the correct one, so Composer's InstalledVersions API reports packages correctly.

• how would you do that though?
• how do you define what is the "correct composer.json": what if a bin tool is relying of the InstalledVersions from the bin directory not the root one?

From a brief glance, it looks like Versions::* is relying on the vendor dirs registered to the class loaders, which hints its likely related to what autoloader is autoloaded. #141 seems to confirm this.

To be clear: I do not mean there is nothing more to do here, but I don't think I understand the problem neither.

from composer-bin-plugin.

Yes, you are right! See #141 (comment)

from composer-bin-plugin.