Graphql Mapper Laravel Package

Product Decisions This Supports

• Accelerating GraphQL adoption for legacy Laravel/PHP systems: Justifies leveraging this package to avoid reinventing the wheel for schema generation, especially if the team lacks GraphQL expertise. Reduces time-to-market for exposing existing Eloquent models via GraphQL.
• Build vs. Buy for GraphQL tooling: Supports a "buy" decision for schema mapping (vs. custom development) when the use case is simple (e.g., direct model-to-schema translation without complex resolvers or subscriptions).
• Roadmap for incremental GraphQL rollout: Enables a phased approach—start with basic CRUD queries over Eloquent models, then layer in custom resolvers or migrate to a more modern solution (e.g., graphql-php + custom mapping) later.
• Use cases:
  • Internal tools or admin panels where GraphQL is a lightweight alternative to REST.
  • Prototyping GraphQL APIs before committing to a full schema-first design.
  • Systems where the team prioritizes speed over long-term maintainability (e.g., side projects or MVPs).

When to Consider This Package

• Adopt if:

  • Your Laravel app uses Eloquent models and you need a quick, zero-config GraphQL layer for them.
  • You’re not using Doctrine ORM (this package is Doctrine-focused; Eloquent support may require workarounds).
  • Your GraphQL needs are basic: No subscriptions, no complex nested resolvers, and no custom directives.
  • You’re okay with abandoned maintenance (last release in 2016) and potential compatibility issues with newer Laravel/GraphQL-PHP versions.
  • You’re evaluating low-risk, short-term solutions (e.g., for a proof of concept).

• Look elsewhere if:

  • You need modern GraphQL features (e.g., subscriptions, federation, or persistent queries).
  • Your team requires long-term support or active maintenance.
  • You’re using non-Doctrine databases (e.g., MongoDB, custom SQL) or need advanced query optimization.
  • You’re building a public API where schema stability and tooling (e.g., GraphQL Playground, validation) are critical.
  • You’re already using or planning to use Lighthouse, GraphQL-YAML, or Relay-compatible tools for schema design.

How to Pitch It (Stakeholders)

For Executives: "This package lets us expose our Laravel app’s data via GraphQL with minimal effort—think of it as a ‘GraphQL wrapper’ for our existing Eloquent models. It’s like adding a lightweight API layer without rewriting our backend. Best for internal tools or quick prototypes where we can iterate fast. Trade-off: It’s not actively maintained, so we’d need to monitor compatibility as we scale."

For Engineering: *"Pros:

• Zero-config for simple schemas: Auto-generates GraphQL types from Eloquent models (if Doctrine-compatible).
• Fast integration: Just define a YAML mapping file and it works with graphql-php.
• Good for throwaway or low-risk projects: Avoids the upfront cost of designing a full schema.

Cons:

• Abandoned: Last update in 2016—may need patches for Laravel 8+/9+ or GraphQL-PHP v14+.
• Limited to basic queries: No subscriptions, no complex resolvers, and no built-in tooling (e.g., no GraphQL Playground integration).
• Doctrine-centric: Eloquent support might require manual tweaks.

Recommendation: Use this for a spike to validate GraphQL’s value for our use case. If it works, we can later migrate to a more maintained solution (e.g., Lighthouse) or build custom resolvers on top of this foundation."*