Contrib.social

Support graphql compose configuration at the subfield level

Open on Drupal.org →
Created on 19 May 2025, 1 day ago

Problem/Motivation

The current graphql support does not allow configuration at the subfield level which inhibits the same abilities at the field level to enable/disable subfields and define a specific schema name.

Proposed resolution

  1. Add a form alter in the custom_field_graphql.module file that adds additional settings to the form
  2. Modify the graphql schema to support these new settings
  3. Modify the schema and field type logic to account for these settings
  4. Add an install hook that checks for multi-word subfield names to explicitly set those values as the subfield schema name to prevent breaking existing apis.

Remaining tasks

Implement the proposed resolution and modify test coverage to validate these additions.

User interface changes

Graphql compose settings for custom fields will have additional subfield details elements for setting enabled/disabled (enabled set by default) and schema name. New fields will assume camelCase schema names.

API changes

Assumed camelCase schema names for subfields if not overridden. Subfields with unchecked 'enabled' in settings will not be returned in api results.

✨ Feature request
Status

Active

Version

3.1

Component

User interface

Created by

🇺🇸United States apmsooner

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024