- What is formapro/yadm and why are its descriptions conflicting?
- The supplied material describes formapro/yadm three different ways: a lightweight Doctrine DBAL data mapper, a Yandex.Direct API client, and a MongoDB document mapper/ODM. Treat that inconsistency as a red flag and verify the actual repository, composer.json, README, and release history before designing around it. Do not commit architecture until the package identity and supported persistence model are confirmed.
- Is formapro/yadm a Laravel package or a standalone PHP library?
- It should be treated as a standalone PHP library, not a first-class Laravel package with documented Laravel conventions. Laravel integration will likely require custom service provider bindings, configuration, connection lifecycle management, repository interfaces, and health checks. Validate autoload behavior and Composer dependency resolution in a small proof of concept first.
- Which Laravel and PHP versions does formapro/yadm support?
- The provided evaluation does not confirm supported Laravel or PHP versions, and the last release was 2019. That predates PHP 8.x and several newer Laravel major versions, so compatibility is uncertain. Pin PHP, Laravel, MongoDB driver, and server versions in Composer and CI, then run a compatibility matrix spike.
- How do I install formapro/yadm with Composer in Laravel?
- Install it through Composer after confirming dependency resolution against your PHP version, Laravel version, and database driver requirements. Because Laravel integration is custom, add your own provider and configuration bindings rather than assuming package discovery. Test autoloading and connection lifecycle in a minimal application before expanding usage.
- Does formapro/yadm require MongoDB and ext-mongodb?
- The technical evaluation describes Yadm as a MongoDB document mapper/ODM, so plan around ext-mongodb and MongoDB driver compatibility. Validate connection strings, TLS and authentication, replica-set behavior, and serialization of dates, UUIDs, and binary data. Driver API drift is a key risk given the stale release timeline.
- Can formapro/yadm replace Eloquent for relational models in Laravel?
- It should not replace Eloquent for core relational domains. Use it only behind application-owned repository interfaces for an isolated MongoDB read model, projection store, or bounded context. Keep controllers and domain code dependent on contracts rather than Yadm classes.
- How should I configure formapro/yadm in a Laravel service?
- Create an internal wrapper package that adds a Laravel service provider, configuration file, repository implementations, and telemetry. Inject configuration and connections through Laravel’s container, and avoid relying on undocumented global state. Add health checks and operational runbooks before production use.
- How do I test formapro/yadm repositories in a Laravel app?
- Test repository contracts with representative documents and integration tests against the supported MongoDB server and driver combination. Cover hydration edge cases, embedded documents, references, polymorphism, partial hydration, and bulk operations. Also run dual-read comparisons and performance baselines against your current data path.
- Is formapro/yadm safe for production and who maintains it?
- Production risk is high: the last release was 2019, repository provenance is unknown, stars are low, and upstream maintenance is unclear. Treat the package as internally owned software with a fork or vendored patch path, security review, escalation owner, and support policy. Start with a canary and a rollback path to native driver code.
- What are alternatives and exit paths to formapro/yadm?
- Evaluate Doctrine MongoDB ODM, native MongoDB driver repositories, or another maintained ODM that fits your PHP and Laravel versions. Choose based on ownership, compatibility, performance evidence, and long-term support. If migrating from another ODM, build anti-corruption adapters rather than rewriting domain entities immediately.