Omit schema definitions for unused fields

Created on 24 July 2024, 4 months ago

Updated 12 August 2024, 3 months ago

Problem/Motivation

Currently the schema includes all possible field types that are used in all fields of the enabled entity types. This potentially includes dozens of field types for fields that are not exposed to GraphQL. Let's only include what is strictly necessary.

Steps to reproduce

Add a large number of different fields to a Node content type.
Only expose the node label in the GraphQL server.

Expected result

The schema should not include any field definitions, since the label field is a basic String scalar type.

Actual result

A large number of unused field types are included in the schema.

Proposed resolution

Only include the field types for fields that are actually exposed to GraphQL.

✨ Feature request

Status

Fixed

Version

1.0

Component

Code

Created by

🇧🇬Bulgaria pfrenssen Sofia

Live updates comments and jobs are added and updated live.

Merge Requests

!14Omit schema definitions for unused fields
Merged
🇧🇬Bulgaria pfrenssen
updated 4 months ago

Comments & Activities

Issue created by @pfrenssen
Merge request !14Only generate field types for exposed fields. → (Merged) created by pfrenssen
Status changed to Needs review 4 months ago7:30am 25 July 2024
Comment 4 months ago →
🇧🇬Bulgaria pfrenssen Sofia
First commit to issue fork.
Pipeline finished with Skipped
4 months ago
#237326
Comment 4 months ago →
System Message

dulnan → committed 9b0af176 on 1.0.x authored by pfrenssen →
Issue #3463646 by pfrenssen: Omit schema definitions for unused fields
Status changed to Fixed 4 months ago12:18pm 29 July 2024
Comment 4 months ago →
🇨🇭Switzerland dulnan
Comment 3 months ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024