-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server: support remote relationships to unions, interfaces and enum types #6080
Merged
codingkarthik
merged 13 commits into
hasura:master
from
codingkarthik:remote-relationships-unions-interfaces
Oct 29, 2020
Merged
Server: support remote relationships to unions, interfaces and enum types #6080
codingkarthik
merged 13 commits into
hasura:master
from
codingkarthik:remote-relationships-unions-interfaces
Oct 29, 2020
Conversation
This file contains 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
tirumaraiselvan
approved these changes
Oct 27, 2020
jberryman
requested changes
Oct 27, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple nits and that request for a good comment
Co-authored-by: Brandon Simmons <brandon.m.simmons@gmail.com>
codingkarthik
changed the title
Server: support remote relationships to unions and interfaces types
Server: support remote relationships to unions, interfaces and enum types
Oct 28, 2020
jberryman
approved these changes
Oct 28, 2020
Deploy preview for hasura-docs ready! Built with commit 21b4ff8 |
codingkarthik
added a commit
to codingkarthik/graphql-engine
that referenced
this pull request
Nov 6, 2020
…ypes (hasura#6080) * add support for joining to remote interface and union fields * add test for making a remote relationship with an Union type * add CHANGELOG * remove the pretty-simple library * remove unused imports from Remote.hs * Apply suggestions from code review Co-authored-by: Brandon Simmons <brandon.m.simmons@gmail.com> * support remote relationships against enum fields as well * update CHANGELOG Co-authored-by: Brandon Simmons <brandon.m.simmons@gmail.com> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
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.
fixes #5875
This PR adds support to joining remote fields of union and interface types. Earlier, we used to throw a validation error if the remote field is of either of the above mentioned types.
Description
Changelog
CHANGELOG.md
is updated with user-facing content relevant to this PR. If no changelog is required, then add theno-changelog-required
label.Affected components
Related Issues
Solution and Design
Steps to test and verify
Limitations, known bugs & workarounds
Server checklist
Catalog upgrade
Does this PR change Hasura Catalog version?
Metadata
Does this PR add a new Metadata feature?
run_sql
auto manages the new metadata through schema diffing?run_sql
auto manages the definitions of metadata on renaming?export_metadata
/replace_metadata
supports the new metadata added?GraphQL
Breaking changes
No Breaking changes
There are breaking changes:
Metadata API
Existing
query
types:args
payload which is not backward compatibleJSON
schemaGraphQL API
Schema Generation:
NamedType
Schema Resolve:-
null
value for any input fieldsLogging
JSON
schema has changedtype
names have changed