feat: resolve all pivot attributes #2464
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.
Changes
This PR allows users to expose all pivot fields in connections in a new field
pivot
which resides next tonode
andcursor
. This could be helpful in the following situation:Now we can query the user and his rated posts like this:
Since the
pivot
field is now of typeUserPost
we can easily update the rating in these entities on the client (i.e. optimistic update) without fetching the whole list again.Breaking changes
The change will break things in the unlikely situation that there is a
pivot
field within thepivot
field.