Weave Code
Association Resolver Bundle Laravel Package
ibrows/association-resolver-bundle
A Symfony bundle that resolves entity associations from identifiers or request data, letting you map incoming values to related Doctrine entities through configurable resolvers. Simplifies form binding, imports, and API payload handling with less boilerplate.
At a glance
Frequently asked questions about Association Resolver Bundle
- Can I use ibrows/association-resolver-bundle in a Laravel application?
- No. It is a Symfony bundle built around bundle registration, DI container compiler passes and the EventDispatcher, with no Laravel service provider, auto-discovery or configuration surface a Laravel developer would recognise. The resolver logic depends on Doctrine ORM class-level annotations, so you would have to port it rather than install and configure it. Treat it as a reference implementation of the metadata-driven association resolution pattern.
- Is ibrows/association-resolver-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It resolves Doctrine ORM entity associations from identifiers or request data by reading class-level annotations, using configurable resolvers. Laravel's service providers, Eloquent relationship layer and PHP 8 attributes share no mechanical overlap with that design, so dropping it into a Laravel app is a porting exercise.
- How do I install ibrows/association-resolver-bundle with Composer?
- The technical recommendation is not to add it to composer.json in a Laravel codebase. Installing it brings Symfony and doctrine/annotations coupling with no Laravel integration, and there is no service provider or config file to register. If you only want the pattern, clone the repository and read the resolver implementation instead of requiring the package.
- Does ibrows/association-resolver-bundle work with Doctrine ORM 3 and PHP 8 attributes?
- High risk. The bundle resolves associations by reading class-level annotations, and Doctrine's annotation driver was deprecated and removed in ORM 3.x in favour of PHP 8 attributes. Any code path relying on doctrine/annotations reading is on a hard expiry clock regardless of framework. There is also no evidence anyone has run it against a modern PHP, Symfony or Laravel stack.
- What is the best Laravel alternative to ibrows/association-resolver-bundle?
- Port the pattern into a small first-party Laravel package: a service provider for bindings, a resolver service, an attribute such as #[ResolvesAssociation] replacing the annotation, and Eloquent relationship methods as the resolution target. The source is small, so this is bounded work and removes Symfony coupling, the abandoned dependency and the annotation deprecation in one move. Also check whether static relationship declarations or a mapping config file solve the problem without runtime resolution.
- Is ibrows/association-resolver-bundle maintained and safe for production?
- It has zero stars and zero dependents, so there is no downstream signal, no maintainer relationship to lean on and no issue history to mine for known breakage. Combined with annotation-driven resolution breaking silently on PHP minor and Doctrine major upgrades, production risk is high. Use it as a prototype or reference only, not as a production dependency.
- How does ibrows/association-resolver-bundle resolve Doctrine entity associations from identifiers or request data?
- It maps incoming identifiers or request values to related Doctrine entities through configurable resolvers that read class-level association metadata. That is convenient for form binding, imports and API payload handling in Symfony applications with less boilerplate. The exact semantics — query-time resolution versus a cached graph, and how bidirectional or circular associations are handled — are underspecified and need to be documented before reuse.
- How do I test a ported association resolver in Laravel?
- Write feature tests that exercise Eloquent relationships and identifier-to-model mapping end to end, plus unit tests for the attribute parsing. Use model factories and an in-memory SQLite connection for fast coverage of bidirectional and circular cases. Explicitly assert behaviour when metadata is missing, because that case is underspecified in the original bundle.
- Should I port ibrows/association-resolver-bundle to Laravel or write my own attribute-driven resolver?
- Port the pattern, not the dependency. A discovery spike of one to two days to document the exact resolution semantics, followed by a three-to-five day port against Eloquent with PHP 8 attributes, covers the source's cases and eliminates Symfony coupling. Decide who owns the ported code after the initial spike, and confirm that person is still around in twelve months.
- What are the risks of annotation-driven association resolution in a Composer package?
- Three concentrated risks: abandonment, since zero stars and zero dependents means no maintainer support or issue history; metadata-layer decay, because annotations were removed in Doctrine ORM 3.x and break silently on upgrades; and reflection-based scanning cold-start cost that is easy to overlook in a prototype. Semantic ambiguity around circular and bidirectional associations adds further risk. Ask first whether you need generic dynamic discovery, which justifies an abstraction, or a one-off mapping between two known models, which does not.
Weaver
How can I help you explore Laravel packages today?