Weave Code
Datatransformation Bundle Laravel Package
rtxlabs/datatransformation-bundle
A PHP data transformation bundle for converting arrays, objects, and API payloads into consistent output using reusable transformers. It offers a structured, extensible way to map and normalize data across your application.
Transforming to or from JSON for Symfony2 REST-Controller
Frequently asked questions about Datatransformation Bundle
- Is rtxlabs/datatransformation-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle. The Bundle suffix, the RtxLabs vendor history, and the original description about JSON transformation for a Symfony2 REST controller all point to Symfony, and it is wired through a DI extension and config tree rather than a Laravel service provider. Treat any listing of it as a Laravel package with suspicion and read the source before adopting it.
- How do I install rtxlabs/datatransformation-bundle with Composer?
- Run composer require rtxlabs/datatransformation-bundle in a scratch branch first, then inspect the resolved PHP and symfony/* constraints in composer.lock. In a Symfony app you also register the bundle in AppKernel or bundles.php depending on the Symfony version. In a Laravel app there is no registration path, so only the standalone mapper classes are realistically reusable.
- Can I use rtxlabs/datatransformation-bundle in a Laravel application?
- Only partially, and probably not as a runtime dependency. The mapper classes may be plain PHP you can instantiate manually, but the bundle's service container wiring, configuration tree, and Symfony-coupled interfaces have no equivalent in Laravel. Laravel API Resources or spatie/laravel-fractal cover the same declarative output-shaping use case with first-class framework support.
- Which PHP and Symfony versions does rtxlabs/datatransformation-bundle support?
- That has to be read from the package composer.json, since the constraints are not stated in the overview. Check the require block for the php and symfony entries, then confirm they do not conflict with the Symfony major already present in your project. Also check the last commit date, because an old constraint often means the package predates current PHP versions.
- Is rtxlabs/datatransformation-bundle safe to use in production?
- Treat it as high risk. It has roughly thirteen GitHub stars and zero dependents, so there is no ecosystem validation, no downstream bug reports, and a single-maintainer bus factor. Undocumented edge cases around nulls, circular entity graphs, and uninitialized lazy proxies are likely, so any real use needs its own test coverage around those paths.
- How does rtxlabs/datatransformation-bundle compare to Laravel API Resources?
- They solve the same problem: assembling a consistent JSON shape from entities and arrays. API Resources ship with Laravel, include pagination and conditional attribute support, and are covered by the framework testing utilities, whereas this package is an unmaintained Symfony bundle with no Laravel integration path. For a Laravel codebase, copy the typed-mapper pattern rather than the dependency.
- Does rtxlabs/datatransformation-bundle have a test suite?
- The overview does not confirm one, so inspect the repository for a tests directory, a phpunit.xml, and CI configuration before trusting it. If there is no suite, budget for writing your own characterization tests around the mappers you actually use. That is the only practical way to catch regressions when you upgrade PHP or Symfony.
- How do I handle circular references or lazy-loaded relations when mapping entities to JSON?
- This is the riskiest area with this package because the behavior is undocumented. Build a small fixture set with a bidirectional relation, a null relation, and an uninitialized Doctrine proxy, then map each one and record the output. If the mappers recurse infinitely or trigger lazy loading, normalize the data into plain arrays before handing it to the transformer.
- What alternatives exist to rtxlabs/datatransformation-bundle?
- In Laravel, use API Resources or spatie/laravel-fractal. In Symfony, use the Serializer component or JMSSerializer, both of which are maintained and support serialization groups and normalization context for controlling output shape. Plain typed transformer classes are also a viable option and remove the third-party dependency entirely.
- How do I migrate away from rtxlabs/datatransformation-bundle?
- Extract the output shape definitions from the mapper classes and rebuild them as Laravel API Resource classes or plain transformer objects, which is days of work rather than weeks. If the mapping logic is genuinely non-trivial, wrap it behind an internal JsonMapperInterface so the vendor package stays behind one seam. Avoid the wrapper if the mappers pull in bundle-internal services, since that turns a temporary shim into permanent scaffolding.
Weaver
How can I help you explore Laravel packages today?