Download the PHP package liquiddesign/lqgraphi without Composer

💫 LqGrAphi

GraphQL API library for Liquid Design ecosystem.

Functions

• Auto types creation from PHP classes to TypeRegister (Storm entities)
• Autoload of Queries, Mutations and Types from namespaces
• Caching of schema, persisted queries and mutations
• Universal CRUD query, mutations and resolvers for generic generation and resolving
• Recursive data fetcher of Storm entities from database based on requested query (highly optimized - makes only one query per entity class - simulating dataloader)

Recommendations

This package works great with extended packages with types for LQD packages:

• https://github.com/liquiddesign/eshop-api
• • https://github.com/liquiddesign/admin-api
• • https://github.com/liquiddesign/security-api

Installation

This package requires PHP 8.2 or higher.

composer require liquiddesign/lqgraphi

Configuration

Entry point

In you entry point (probably index.php) you need to call handler. You just need to create container and pass it to \LqGrAphi\Handlers\IndexHandler::handle.

Minimal example of index.php:

Sandbox

Apollo Sandbox is enabled by default for debug connections based on environment file.

You can permanently disable it:

Queries and Mutations

Location of queries and mutations is set via config queryAndMutationsNamespace. Query needs to extend \LqGrAphi\Schema\BaseQuery and mutation \LqGrAphi\Schema\BaseMutation.

These types are automatically loaded only first time when schema is created and cached. All other requests uses cached schema, due to that script don't need to create schema for every request and performance is not decreased. This approach has some limitations: Queries and mutations are not registered in container, so you cant use DI. All these classes will receive container as first argument.

Types

Location of types is set via config types. You need to specify all used inputs and outputs here.

For more info visit documentation of webonyx/graphql-php library.

ClassOutput

There is interface \LqGrAphi\Schema\ClassOutput with method getClass. If you use it, TypeRegister will save this mapping ang when you call getOutputType you can simply pass class-string instead of name.

ClassInput

Same as ClassOutput for inputs.

Relations

In outputs, relations are object or list of objects with up to 10 levels of depth. Inputs, on the other end, have always two fields for relation.

One with suffix ID for single relations which takes string (or null if possible). For many relations there is field with suffix IDs which is object with add, remove and replace fields. These fields takes list of strings.

Second, there is always fields with suffix OBJ, which takes directly input object and also updates it. It can also have 10 levels of depth. For many relations there is field with suffix OBJs which takes list of input objects.

Due to limitations of GraphQL where you can´t have union input type, these inputs are always in UpdateInput variant which has all fields optional. Based on ID field, object is created or only updated. This approach loses type safety for required fields when creating object, in this case error will only be caused in runtime.

There is interface \LqGrAphi\Schema\ClassInput with method getClass. If you use it, TypeRegister will save this mapping ang when you call getInputType you can simply pass class-string instead of name from config. Also, TypeRegister will map this input in input objects to relation fields.

Resolvers

Due to caching of whole schema creation, resolvers are isolated from schema and have to resolve request on their own.
There is simple routing mechanism. GraphQL's queries and mutations names uses lower-camelCase.
Name is parsed as first word in resolver class name and rest is function name.
Example: productGetMany is parsed as ProductResolver and function getMany.

Router that parses name to resolver and function uses on-demand cache.

Signature of every resolver function must be:

Recommended way of configuration:

Cache

Handler is using cache to remember queries and mutations. If you send same query twice, it will be resolved from cache and directly passed to resolver. This approach significantly increases performance. Data returned from resolver are validated only with first request. This approach is not safe, when resolvers are not fully tested.

You can also pass queryId directly instead of query. Queries are hashed by md5, so you can just hash you query with md5 and send it as queryId. But remember, that you still need to send at least one request with query to validate it.

CRUD

You can write your types and queries by yourself, but most of the time you just want to take existing entity and make crud operations for it.

At that point comes \LqGrAphi\Schema\CrudQuery and \LqGrAphi\Schema\CrudMutation.

First, create query class

then create output, create and update types with use of helpers:

register your types namespace in config and lastly create resolver

That's all, you can query one, many or collection and mutate create, update and delete operations.

Helpers for CRUD

To help working with API there is some automatic improvements

• All array outputs are encapsulated in object with key data and onPageCount
• There is universal input objects for sorting, paging and filtering

Filtering

Filters are input fields of type JSON, which are parsed to repository allowed filter functions. Due to this, filters are dynamically typed.

Fetch result

There is universal fetch function. You just need to pass collection with ResolveInfo. It will take care of retrieving only data you asked in most efficient way.

Language mutations

If you need to use different language mutation, you can use HTTP header "Accept-Language". System will set detected language (if supported) as primary language for all SQL queries. If no language in "Accept-Language" header is supported, then primary language from settings is used.

Roadmap

2023

• ✅ Persisted queries with cache
• ❗New type loading system to bring better DX
  • No need to register types
  • Load types from namespace
  • Refactor TypeRegister
• Security - guards, login
• Automatic testing

Developers info

Project uses PHPStan (level 8) and PHP-CS-Fixer for code quality.