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