Compound key support in federation #1011
Merged
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.
Compound keys aren't currently supported in the federation plugin, but are allowed per the Apollo spec. This patch adds support by modifying the federation plugin to handle a list of key fields on an entity rather than a single top-level key field. It will now look for "findEntityNameByKeyField1AndKeyField2..." in the resolver, rather than the original "FindEntityNameByKeyField". The change does not support more complicated FieldSets in the key, such as nested selections.
We are using this internally with Go services that use compound keys in federation.
References:
I have: