Repository navigation
Skip auto-installing when the root package's extra.discovery is enough #237
Description
Activity
thanks for the discussion in #236 . a workaround for now would be to do the
composer config allow-plugins.php-http/discovery falsefrom the readme, correct? and have the internal package provide the required*-implemenationinformation for composer.I agree we can't check just for the
*-implementationof installed packages because that still does not tell which classes to use. and scanning the code for implementing interfaces is too fragile (and a performance problem when no caching mechanism is available). while afaik java does support this sort of self-registration and autodiscovery mechanisms, i agree with not going that far.the change suggested here would be that the existing configuration to chose which class to use for which psr factory also accepts unknown classes in addition to the well-known ones, right? that seems consistent with what we have and non-surprising.
(btw there is some doc that is only in the readme but missing from https://docs.php-http.org/en/latest/discovery.html, we should sync the 2 places when we do this change)composer config allow-plugins.php-http/discovery false
correct!
the existing configuration to chose which class to use for which psr factory also accepts unknown classes in addition to the well-known ones
This works already!
The only thing missing is skipping the installation of well-know packages when all interfaces of the virtual package are listed.oh even better. yeah then its not much left to be done 👍
and i just realized that you just added the pinning recently. neat, thanks!
Implemented in #239
Here is an idea that popped up in #236 and that builds on #232.
When the root package configures this:
then we shouldn't need auto-installing any extra packages for this virtual package.
Same when listing individual interfaces:
In this case, we should verify that all the interfaces required to fulfill one of the supported
*-implementationare listed.