elephentity / graphql
Experimental Framework-independent GraphQL integration for the Elephentity PHP runtime.
Requires
- php: >=8.3
- elephentity/runtime: ^0.10 || ^0.11
- webonyx/graphql-php: ^15.0
Requires (Dev)
None
Suggests
None
Provides
None
Conflicts
None
Replaces
None
This package is auto-updated.
Last update: 2026-09-27 20:32:12 UTC
README
Experimental framework-independent GraphQL integration for Elephentity's PHP
runtime, extracted from Clog's standalone backend. It builds a webonyx/graphql-php
schema without WordPress or WPGraphQL.
The Composer package name is elephentity/graphql, preserving Clog's existing
namespace and package layout. It requires PHP 8.3+, elephentity/runtime ^0.10 || ^0.11 and
webonyx/graphql-php ^15.0. Runtime 0.11 support is prepared for
0.1.0-alpha.2; 0.1.0-alpha.1 requires runtime 0.10.
Components
SchemaBuilder: objects, inputs, interfaces, enums, connections and mutations.Manifest: the compiled entity, query, field and mutation descriptions.Registration: maps those descriptions to resolver configurations.RelayandResolver: global IDs and connection results.
Storage remains behind the Elephentity runtime, so GraphQL does not depend on the SQLite package. The same generated PHP entities can be exposed through this package with an appropriate runtime and storage adapter.
Status and validation
This prototype follows Clog's feature/standalone-sqlite work.
Provenance identifies the source by file hashes, now verified
against Clog commit fb57b3c.
The inherited source license is preserved in CLOG-LICENSE.
Clog's adapter conformance, schema-upgrade, integration and HTTP suites pass with
fresh Composer dependencies on runtime 0.10.0 and 0.11.0. With sibling
elephentity-sqlite and Clog checkouts, rerun the matrix using:
python3 ../elephentity-sqlite/tools/test-clog.py ~/Projects/clog python3 ../elephentity-sqlite/tools/clog-status.py ~/Projects/clog
The runner requires Podman, network access for Composer, Clog's PHP image and a
built client. Add --package-version 0.1.0-alpha.2 after publishing both integration
packages to validate the published artifacts. See
runtime compatibility validation for release evidence.
See extraction notes for behavior still implemented in Clog and the work required before a general release.