- Is tadcka/mapper-bundle compatible with Laravel?
- No. It is a Symfony bundle, not a Laravel package: it registers services through a Symfony DI extension and configuration tree and expects a Symfony kernel to boot it. Laravel has no equivalent bundle registration, so you cannot Composer require it into a Laravel application and use it as-is. Any Laravel use would require a fork or bridge that strips the Symfony scaffolding.
- How do I install tadcka/mapper-bundle with Composer?
- It is distributed as a Symfony bundle, so installation is intended for a Symfony application followed by bundle registration. There is no supported Composer installation path for Laravel. Its 2015-era Composer constraints may also block resolution against modern PHP versions.
- Does tadcka/mapper-bundle support Laravel 10 or Laravel 11?
- There is no evidence of Laravel support. The last release was 2015-10-12 and targets PHP 5.x and Symfony 2.x, while Laravel 10 and 11 require modern PHP. Its constraints and runtime code are likely incompatible without a port.
- What is tadcka/mapper-bundle used for?
- It is intended for mapping data between objects and arrays, simplifying DTO conversion and decoupling domain entities from application layers. The brief description, 'Linking the different elements,' suggests the underlying idea is a generic object-to-object mapper. The delivered artifact, however, is Symfony-coupled scaffolding around that logic.
- Can I use tadcka/mapper-bundle with PHP 8?
- Not as-is with confidence. Code from 2015 targets PHP 5.x, and PHP 8 can surface removed functions, dynamic property deprecations, and nullable or type signature changes. You would need to audit and port the framework-free core before relying on it.
- Is tadcka/mapper-bundle maintained?
- No. Its last release was 2015-10-12, making it roughly a decade stale, and it has zero stars and zero dependents. There is no active upstream to absorb future PHP or framework upgrades. Treat it as a reference implementation rather than a maintained dependency.
- What are alternatives to tadcka/mapper-bundle for Laravel DTO mapping?
- Look for actively maintained Laravel-native DTO or data-mapping packages, or write a small in-house mapper. Because this package is Symfony-coupled and abandoned, a focused mapper of roughly 200 to 400 lines is likely cheaper than maintaining a fork. The right choice depends on whether you need DTO-to-entity mapping, Eloquent hydration, or cross-system entity linkage.
- How do I migrate tadcka/mapper-bundle mapping logic to Laravel?
- Extract rather than install. Pull the source directly, isolate the framework-free core such as mapper interfaces, mapping definitions, and concrete mapping classes, then re-run that logic against PHP 8.2+ in a bare script. After proving portability, reimplement it behind a Laravel-native Mapper contract bound in a service provider instead of wrapping Symfony DI.
- Is it safe to use tadcka/mapper-bundle in production?
- It carries high technical risk because it is unmaintained, has zero adoption, and contains decade-old code. There is no evidence of production use or battle-testing, and an unvetted old package should not enter the dependency graph without a security review. Adopting it also creates a permanent fork ownership obligation.
- How should I test or validate tadcka/mapper-bundle before adopting it?
- Audit the source and run the isolated core logic in a bare PHP 8.2+ script to surface removed functions and type incompatibilities. Check its Composer constraints against your PHP and Laravel versions, and verify whether mapping rules are documented or must be reverse-engineered. Because there are no dependents, you will own all validation and fixes.