GraphQL Library 3 Release Notes

execute() accepts a single params object with schema, query, variables, and context.

maxDepth and maxFieldsCount in the params object reject queries that are too deep or too large. See execute.

TypeScript type definitions for all three modules are published as @enonic-types/lib-graphql on npm, versioned in step with the library. See TypeScript for setup.

The type definitions are generated from the library’s TypeScript source, so they cannot drift from the shipped modules.

The @enonic-types/lib-graphql 3.0.0 setup that listed the package only in types could not resolve /lib/graphql imports. The package now needs paths entries as well; see TypeScript.

The modules are compiled from TypeScript, and their exports are read-only. Assigning to an export, for example to mock execute in a test, throws; replace the whole module instead. Overriding encodeCursor no longer changes the cursors of types created by createConnectionType.

A bundler or compiler default import such as import graphQlLib from '/lib/graphql' no longer resolves to the module. Use require(), a namespace import (import * as graphQlLib from '/lib/graphql'), or named imports.

The positional form execute(schema, query, variables, context) is deprecated and will be removed in the next major version. Use execute({schema, query, variables, context}) instead.

Added compatibility with Enonic XP 8.

Updated the underlying GraphQL Java libraries used to build and execute schemas.

Queries deeper than 100 levels or with more than 100000 fields are rejected.

Replaced the end-of-life RxJava dependency with a JDK Flow-based subscription implementation while retaining the /lib/graphql-rx JavaScript helpers.

Subscription publishers preserve the XP execution context by delivering events on the publishing thread.

The minimum required Enonic XP version is 8.0. Applications running on XP 7 must continue using GraphQL Library 2.x.