Simplify Content Type setup to extend Relationship #1094
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.
I was struck with inspiration 🛰💥, and realised that the
Content
type should extend theRelationship
type (instead ofText
), which means all the tricky stuff I was trying to do with manually triggering nested mutations can be handled by KS5 like normal.This also greatly simplifies the next bit of work which is querying for the data, plus enables the
from
back-linkRelationship
to work out of the box.