- What is hecht-a/graphql-orm used for in Laravel?
- It adds an Eloquent-backed ORM layer for GraphQL, mapping models and relationships to GraphQL types so you can expose database structure with fewer hand-written resolvers. It is aimed at schema-driven APIs where nested relationships and filtering should follow Laravel conventions. However, validate Laravel fit carefully because the available technical assessment flags Symfony-first signals.
- How do I install hecht-a/graphql-orm with Composer?
- Install it as a Composer dependency and follow the package registration and schema configuration instructions for your framework version. The supplied context does not include exact install commands, so check the README and release notes before adding it to a project. The v5.10.1 note is only a visibility change to countMatching(), not an installation requirement.
- Does hecht-a/graphql-orm support Laravel 10 or Laravel 11?
- The supplied context does not list supported Laravel versions, so do not assume Laravel 10 or 11 compatibility without checking composer.json and the README. The technical assessment warns that the package looks Symfony-first, so confirm framework support before adopting it in a Laravel app. If Laravel support is not explicit, treat it as unverified.
- Is hecht-a/graphql-orm a Symfony package or a Laravel package?
- The overview markets it as a Laravel-friendly GraphQL ORM, but the technical evaluation found Symfony vocabulary in consecutive releases, including DebugClassLoader, WebProfiler, and Twig references. That strongly suggests a Symfony-first package where Laravel consumers may be a poorer fit. Confirm your host framework before closing the evaluation.
- How does countMatching() in GraphqlEntityRepository affect upgrades?
- In v5.10.1, GraphqlEntityRepository::countMatching() was de-internalized, so it is no longer marked internal and no longer emits the related debug deprecation when stubbed in tests. That creates new supported public surface, even though profiling, resolver execution, schema shape, and mapping semantics are unchanged. If you override or call it, align signatures and treat it as API.
- Will upgrading from 5.2.0 to 5.10.1 break my test suite?
- The patch itself is trivial, but jumping eight minor versions plus a patch means absorbing the cumulative changelog, not just the countMatching() change. If your suite ratchets deprecation counts or asserts on deprecation notices, baselines may need to be lowered because the internal-method deprecation disappears. Inventory GraphqlEntityRepository stubs before bumping.
- Do I need to change configuration when upgrading hecht-a/graphql-orm?
- The v5.10.1 change introduces no config migration, no removals, and no new deprecations. The main upgrade task is test hygiene around deprecation baselines and repository stubs. Review the full v5.3.0 through v5.10.1 changelog for cumulative configuration or behavior changes before planning the bump.
- Can I use hecht-a/graphql-orm in production?
- The package is described as an Eloquent-backed GraphQL ORM for exposing models and nested relationships with less resolver boilerplate, but the technical assessment says it is incrementally growing public API and may be Symfony-first. Production use should wait for confirmed Laravel support, a reviewed cumulative changelog, and a decision on whether countMatching() is a stable extension point. Avoid building production logic on newly de-internalized methods without upstream confirmation.
- How do I test a Laravel app that uses hecht-a/graphql-orm?
- Test schema mapping, nested relationship resolution, filtering, and query behavior through your GraphQL endpoint rather than only unit-testing internals. If you stub GraphqlEntityRepository, check whether you rely on countMatching() and align the double with the now-public signature. Also review deprecation thresholds because the v5.10.1 de-internalization can silence a prior notice.
- What are alternatives to hecht-a/graphql-orm for Laravel GraphQL APIs?
- Common alternatives include dedicated Laravel GraphQL packages and hand-written resolver layers, but the best fit depends on whether you need Eloquent model mapping, schema generation, or a more manual typed schema. Because the technical assessment questions this package's Laravel fit, compare it against actively maintained Laravel-first GraphQL tools and confirm framework support. Evaluate maintenance activity, public API stability, and test integration before choosing.