Add support for lists with no fields in GraphQL#9254
Merged
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
dcousens
force-pushed
the
empty-lists
branch
7 times, most recently
from
ba20efc to
d7fe8a3
Compare
dcousens
force-pushed
the
empty-lists
branch
2 times, most recently
from
96ec297 to
8a9b813
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request addresses the issue where lists in GraphQL may have no fields that should be publicly described in the GraphQL.
This scenario can come up for lists with items that completely derive their content from other sources, and thus no fields need be exposed; but you may still want to support users to create items in these lists.
Previously, developers worked around this problem with custom mutations or by retaining at least one field, relevant or not. This pull request eliminates the need for these workarounds by adding support using an empty object GraphQL scalar.