Implement connect, disconnect and delete operations for nested mutations upon MorphTo relationships
#879
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
spawnia
requested review from
alberthaff,
chrissm79 and
olivernybroe
and removed request for
chrissm79
olivernybroe
approved these changes
Aug 7, 2019
spawnia
changed the title
connect and disconnect operations for nested mutations upon MorphTo relationshipsconnect, disconnect and delete operations for nested mutations upon MorphTo relationships
alberthaff
approved these changes
Aug 7, 2019
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.
Related Issue/Intent
Allows connecting and disconnecting polymorphic associations for a MorphTo relation using nested mutations.
Changes
Implement
connectanddisconnectThe GraphQL Specification does not support Input Union types,
for now we are limiting this implementation to
connectanddisconnectoperations.Let's see which one of the current RFC's makes it and base the implementation of
createandupdateupon that. graphql/graphql-spec#114Breaking changes
Nope