Add nested key entity support for GraphQL Federation#1476
Open
JBodkin-Amphora wants to merge 1 commit into
Open
Add nested key entity support for GraphQL Federation#1476JBodkin-Amphora wants to merge 1 commit into
JBodkin-Amphora wants to merge 1 commit into
Conversation
Signed-off-by: James Bodkin <james.bodkin@amphora.net>
436ea02 to
d0ce0fb
Compare
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
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 adds support for nested keys in GraphQL Federation when using the EntityMapping annotation. Additionally, isOmitted is always set to false for entity mapping, as the GraphQL Gateway will not send requests when the object is null
NB: I'm not able to run the full build locally as I'm unable to install Java 21.