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