- Is symfony-notes/object-transformer-bundle compatible with Laravel?
- No. It is a Symfony bundle, not a Laravel package, so its core value, the container wiring, does not function in Laravel. Laravel consumes individual Symfony components but has no bundle kernel, no bundles.php, and no compiler passes, so the bundle's service definitions are never registered. The underlying ObjectTransformer library may still be usable in Laravel if it is framework-agnostic.
- Can I just composer require a Symfony bundle in a Laravel app?
- Composer will usually install it, but nothing will boot it. Laravel never registers Symfony bundles, so the extension class, service aliases, and configuration tree sit unused in vendor. You end up carrying a dependency you cannot leverage, so require the core library instead.
- How do I use the ObjectTransformer in a Laravel application?
- Require the core symfony-notes/object-transformer library rather than the bundle, then register a singleton or scoped binding in AppServiceProvider or a dedicated package provider. Expose it behind a small internal interface so the implementation can be swapped without touching callers. Prove it on one concrete mapping, such as an Eloquent model or API response to a DTO, before spreading it across the app.
- What does the Object Transformer Bundle actually do?
- It integrates the ObjectTransformer library into Symfony's dependency injection container through a bundle class and service configuration. The goal is reusable, configurable transformers for mapping objects, DTOs, and arrays. That integration layer is exactly the part that has no analogue in Laravel.
- Does it support Laravel 11 and PHP 8.1+?
- There is no published compatibility matrix, CI status, or PHP and Laravel version statement in the available information, so support cannot be assumed. Run composer why-not against your target Laravel and PHP versions to see what Composer actually resolves. Treat any constraint you infer as unverified until the maintainer documents it.
- What are the best Laravel alternatives for DTO and object transformation?
- spatie/laravel-data is the established choice, offering attribute-based mapping, nested hydration, validation, and first-class Laravel integration. spatie/data-transfer-object is a lighter option, and hand-written fromArray and toArray mappers or Illuminate casts handle simple cases cleanly. Because this problem is already well solved, a new dependency needs a clear, demonstrable advantage.
- Will the bundle's Symfony version constraints conflict with Laravel's pinned Symfony components?
- This is a genuine risk. The bundle will declare Symfony ^5, ^6, or ^7 constraints, while Laravel pins specific Symfony component versions per release, so Composer may resolve fine, fail, or force downgrades. Check with composer why-not before committing, and prefer the core library if it only depends on psr/container or nothing framework-specific.
- Is symfony-notes/object-transformer-bundle production ready?
- The packaging signals are weak: zero stars, zero known dependents, no visible CI, no security review history, and a vendor namespace that reads as a personal notes project. That does not prove the code is bad, but there is no community validation or maintenance track record to lean on. For anything user-facing, assume you would own the maintenance burden.
- How should I test object transformations in a Laravel app?
- Write feature tests that assert a known input produces an expected DTO, plus failure-path tests for missing keys, nulls, and type mismatches. If you adopt a third-party transformer, wrap it in your own interface and test the interface so the implementation can change without breaking callers. Realistic fixture payloads catch nested hydration and coercion differences that unit tests with tiny arrays miss.
- What license does the package use, and can I use it commercially?
- The LICENSE file in the GitHub repository is the authoritative source, so check it before adopting. Note that the vendor name reads as an individual notes project rather than an organisation with a support commitment, which matters more than the license text for long-term commercial use. If licensing or support terms are unclear, treat that as a blocker rather than a detail.