tyhpdef / php-http-client-common
Tyhp type definitions for php-http/client-common 2.7.3.
Package info
github.com/tyhpproject-packages/php-http-client-common
Type:metapackage
pkg:composer/tyhpdef/php-http-client-common
Requires
- tyhpdef/php-http-client-common-impl: ~2.7.3.0
Requires (Dev)
None
Suggests
None
Provides
None
Conflicts
None
Replaces
None
README
tyhpdef/php-http-client-common
Tyhp type definitions for php-http/client-common 2.7.3.
composer require --dev tyhpdef/php-http-client-common:2.7.3
This is a metapackage. Composer also installs tyhpdef/php-http-client-common-impl (type files).
Require this name, not tyhpdef/php-http-client-common-impl.
See https://tyhplang.com.
Maintain php-http/client-common? Ship the types yourself
If you are a Packagist maintainer of php-http/client-common, you can take over these
types.
Copy _tyhpdef/ from tyhpdef/php-http-client-common-impl (Apache-2.0; keep the NOTICE).
Then either:
- Bundle the files in
php-http/client-commonand setextra.tyhp.packageon thatcomposer.json, plus"replace": { "tyhpdef/php-http-client-common": "self.version" }, or - Publish a sibling types package under your vendor, versioned with
php-http/client-common(sameX.Y.Z). Setextra.tyhp.packagethere,requirephp-http/client-commonwith a real constraint,"replace": { "tyhpdef/php-http-client-common": "self.version" }, and setextra.tyhp.tyhpdefonphp-http/client-commonto your sibling’s Composer name.
Ship that to Packagist first, then open an issue:
https://github.com/tyhpproject/tyhp-runtime-src/issues/new?template=tyhpdef-ownership.yml
We verify Packagist ownership and that the types parse and cover the PHP
API, then stop publishing community tags for those versions. We do not
transfer the tyhpdef/php-http-client-common Packagist name.
Full process: TYHPDEF_OWNERSHIP.md in
https://github.com/tyhpproject/tyhp-runtime-src