- Is fabricio872/api-modeller-bundle a Laravel package?
- No. It is a Symfony bundle for modelling foreign APIs as models, and it loads through Symfony's DependencyInjection extension, Configuration tree, and services.yaml service definitions. Laravel has no equivalent bundle-loading mechanism, so the package cannot wire itself into a Laravel application the way a service provider would. Treat it as a Symfony-only package.
- Can I install api-modeller-bundle in a Laravel application with Composer?
- A direct composer require is not a viable path. The bundle's services reference Symfony kernel and container interfaces that Laravel does not provide, and the framework's pinned symfony/* polyfill constraints may conflict. Add a likely hard dependency on doctrine/orm and you get two competing persistence abstractions to reconcile. The realistic approach is to read the source as a design reference and reimplement the pattern natively.
- Does api-modeller-bundle depend on Doctrine ORM?
- Very likely yes. Doctrine-like models in a 2022-era Symfony bundle almost always means a hard dependency on doctrine/orm, including the EntityManager, metadata drivers, and hydration internals. Laravel does not ship Doctrine, so installing it alongside Eloquent creates two persistence layers and a nontrivial container reconciliation exercise. Confirm this with the maintainer before any investment.
- What is the Laravel equivalent of modelling a remote API as a model?
- Laravel has no first-party equivalent: Eloquent assumes a local database connection, not a remote HTTP origin. The constituent parts exist separately — Illuminate\Http\Client for transport, the service container for binding, spatie/laravel-data for DTOs, and JsonResource for transformation. The missing piece is a unified foreign-API-as-model layer, which is the actual product opportunity here.
- Is api-modeller-bundle actively maintained?
- No. It has zero stars, zero dependents, a single author, and its last release was 2022-06-23, roughly three years ago. There is no SECURITY.md, no advisory history, and no maintainer SLA. For a package that handles outbound credentials and remote payloads, that is disqualifying for anything touching production data.
- Which PHP and Symfony versions does api-modeller-bundle support?
- There is no stated PHP or Symfony support matrix that can be relied on. Compatibility with modern PHP 8.3 and 8.4 is unverified. Ask the maintainer for the supported matrix and whether any test suite can be run in isolation before committing engineering time.
- How are model mappings defined in api-modeller-bundle — annotations, attributes, YAML, or PHP config?
- The public overview does not say, and this is one of the most important questions for the maintainer. A 2022-era Symfony bundle most likely uses annotations or PHP attributes, but YAML and PHP config are possible. The answer determines whether the mapping logic is runtime-introspectable without the Symfony container.
- How does api-modeller-bundle handle remote API failures?
- Unknown from the public information available, and it matters. Ask whether remote failures surface as typed exceptions or as silent nulls inside hydrated models. In a Laravel reimplementation, prefer explicit typed exceptions plus Http::retry with backoff so failures are visible and bounded.
- Does api-modeller-bundle cache remote responses or maintain an identity map?
- Unverified. Without a caching or identity-map layer, every model access could re-hit the foreign API, which is a latency and rate-limit problem in production. In Laravel, wrap the client with the cache facade, use Http::retry, and keep a request-scoped identity map so repeated lookups resolve locally.
- Should I fork api-modeller-bundle or reimplement the pattern in Laravel?
- The MIT license makes the code forkable and vendorable, so there is no legal friction. But the test posture is unknown, and without meaningful coverage of the mapping and hydration logic a fork may not be salvageable. Given the abandonment and Doctrine coupling, a one-to-two sprint internal reimplementation using Illuminate\Http\Client, DTOs, and JsonResource is usually cheaper than an open-ended dependency.