tyhpdef / dflydev-dot-access-data

3.0.3 2026-10-05 14:35 UTC

Requires

• tyhpdef/dflydev-dot-access-data-impl: ~3.0.3.0

Apache-2.0

• static analysis
• dev

Published on Packagist.org on 2026-10-05 14:35 UTC

README

tyhpdef/dflydev-dot-access-data

Tyhp type definitions for dflydev/dot-access-data 3.0.3.

composer require --dev tyhpdef/dflydev-dot-access-data:3.0.3

This is a metapackage. Composer also installs tyhpdef/dflydev-dot-access-data-impl (type files). Require this name, not tyhpdef/dflydev-dot-access-data-impl.

See https://tyhplang.com.

Maintain dflydev/dot-access-data? Ship the types yourself

If you are a Packagist maintainer of dflydev/dot-access-data, you can take over these types.

Copy _tyhpdef/ from tyhpdef/dflydev-dot-access-data-impl (Apache-2.0; keep the NOTICE). Then either:

1. Bundle the files in dflydev/dot-access-data and set extra.tyhp.package on that composer.json, plus "replace": { "tyhpdef/dflydev-dot-access-data": "self.version" }, or
2. Publish a sibling types package under your vendor, versioned with dflydev/dot-access-data (same X.Y.Z). Set extra.tyhp.package there, require dflydev/dot-access-data with a real constraint, "replace": { "tyhpdef/dflydev-dot-access-data": "self.version" }, and set extra.tyhp.tyhpdef on dflydev/dot-access-data to 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/dflydev-dot-access-data Packagist name.

Full process: TYHPDEF_OWNERSHIP.md in https://github.com/tyhpproject/tyhp-runtime-src