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