You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ExecutableNormalizedField does not respect GraphqlFieldVisibility #4215
Describe the bug ExecutableNormalizedField.forEachFieldDefinition() and getOneFieldDefinition() call type.getField(fieldName) directly, bypassing the schema's configured GraphqlFieldVisibility.
This is inconsistent with other parts of graphql-java (validation, execution) that respect field visibility, and causes issues when:
A custom GraphqlFieldVisibility provides field definitions that differ from what's in the schema type (e.g., placeholder fields, virtual fields, or dynamically-computed fields)
Application code accesses DataFetchingEnvironment.getSelectionSet().getFields() in a DataFetcher
Normalization fails with "No field X found for type Y" because it bypasses the visibility
To Reproduce
Configure a custom GraphqlFieldVisibility that provides virtual/placeholder fields
Execute a query that includes a field only available through the visibility
Access DataFetchingEnvironment.getSelectionSet().getFields() in a DataFetcher
Normalization fails because ExecutableNormalizedField.forEachFieldDefinition() calls type.getField() directly
** Expected Behavior**
ExecutableNormalizedField should use the schema's field visibility when looking up field definitions, consistent with how validation and execution work.
Activity
Samjin commentedon Jan 26, 2026
hi @bbakerman, appreciate if you could take a look.
Samjin commentedon Jan 29, 2026
PR merged