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