tyhpdef / php-amqplib-php-amqplib
Tyhp type definitions for php-amqplib/php-amqplib 3.7.4.
Package info
github.com/tyhpproject-packages/php-amqplib-php-amqplib
Type:metapackage
pkg:composer/tyhpdef/php-amqplib-php-amqplib
Requires
- tyhpdef/php-amqplib-php-amqplib-impl: ~3.7.4.0
Requires (Dev)
None
Suggests
None
Provides
None
Conflicts
None
Replaces
None
README
tyhpdef/php-amqplib-php-amqplib
Tyhp type definitions for php-amqplib/php-amqplib 3.7.4.
composer require --dev tyhpdef/php-amqplib-php-amqplib:3.7.4
This is a metapackage. Composer also installs tyhpdef/php-amqplib-php-amqplib-impl (type files).
Require this name, not tyhpdef/php-amqplib-php-amqplib-impl.
See https://tyhplang.com.
Maintain php-amqplib/php-amqplib? Ship the types yourself
If you are a Packagist maintainer of php-amqplib/php-amqplib, you can take over these
types.
Copy _tyhpdef/ from tyhpdef/php-amqplib-php-amqplib-impl (Apache-2.0; keep the NOTICE).
Then either:
- Bundle the files in
php-amqplib/php-amqpliband setextra.tyhp.packageon thatcomposer.json, plus"replace": { "tyhpdef/php-amqplib-php-amqplib": "self.version" }, or - Publish a sibling types package under your vendor, versioned with
php-amqplib/php-amqplib(sameX.Y.Z). Setextra.tyhp.packagethere,requirephp-amqplib/php-amqplibwith a real constraint,"replace": { "tyhpdef/php-amqplib-php-amqplib": "self.version" }, and setextra.tyhp.tyhpdefonphp-amqplib/php-amqplibto 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-amqplib-php-amqplib Packagist name.
Full process: TYHPDEF_OWNERSHIP.md in
https://github.com/tyhpproject/tyhp-runtime-src