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