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