- Is fabricio872/api-modeller a Laravel package?
- No. Its description points to a Symfony/Doctrine-style abstraction for translating a foreign API into Doctrine-like model objects, and the repository does not show a Laravel service provider, config file, facade, or illuminate dependency. In a Laravel app it would sit beside Eloquent rather than integrate with it, so treat it as a plain PHP library that needs custom glue.
- How do I install fabricio872/api-modeller in a Laravel project?
- Installation is a normal Composer require, but that is the easy part. You must bind the translator into Laravel's container, inject your own HTTP client such as Laravel Http or Guzzle, and decide where hydrated models are cached. Budget this as a small internal integration library, not a drop-in Laravel dependency.
- Does it support Laravel 10 or Laravel 11?
- There is no declared Laravel version support in the package context, and no Laravel-specific integration code is implied. The last release was June 2022, so its Composer constraints are likely to collide with modern illuminate/support versions. Verify dependency resolution in a throwaway app before assuming compatibility.
- What PHP and Doctrine versions does api-modeller require?
- The provided context does not list the declared constraints, so read composer.json before spending time. Because the last release was June 2022, confirm PHP 8.2/8.3 support and doctrine/* constraint ranges explicitly. If Composer resolution fails against your target stack, stop rather than negotiating constraints.
- How does the API-to-model mapping work: attributes, YAML, or hand-written mappers?
- The context does not confirm whether mapping is declarative via attributes or YAML or implemented as hand-written mapper classes. That distinction matters because it decides whether schema drift is a configuration change or a code change. With no documentation beyond the README, treat the source as the specification and inspect it before trusting failure semantics.
- Does api-modeller handle HTTP requests, retries, and authentication?
- The context does not establish that it provides transport, and you should not assume it does. If it owns HTTP transport, you inherit its retry, timeout, and auth behavior, which is usually a non-starter in Laravel. Prefer injecting responses from Laravel Http or Saloon so transport concerns stay in your application.
- Is fabricio872/api-modeller safe to use in production?
- The maintenance risk is high: zero stars, zero dependents, a single maintainer, and a last release in June 2022. There will be no security advisories not because the code is proven safe but because nobody is watching it. For production use, plan to fork it internally, pin PHP versions, and add tests for the payload shapes you depend on.
- Can I use it alongside Eloquent or laravel-doctrine?
- It would sit beside Eloquent, not inside it, giving your Laravel codebase two competing model and persistence idioms. That is an architectural smell unless the foreign API is truly a read-only system of record with no local persistence. With laravel-doctrine, constraint conflicts are more likely because both packages target overlapping Doctrine ranges, so verify explicitly.
- What are better Laravel-native alternatives for typed API models?
- For typed DTOs with validation and casting, spatie/laravel-data is the usual Laravel-native choice. For transport, use Laravel's Http client or Saloon, and hydrate with explicit mapper classes or Attribute casts. These alternatives are maintained and avoid inventing a second model layer.
- How should I evaluate or integrate api-modeller before adopting it?
- Run a one- to two-day spike in a throwaway Laravel app on your target version. The success criterion is clean Composer resolution plus one end-to-end hydration from a mocked payload; if resolution fails, stop. If you proceed, define your own ForeignApiModelTranslator contract, fork and vendor the library as internal/api-modeller, and isolate it so swapping to laravel-data is cheap.