Auto resolve Datastore @connection fields

Is your feature request related to a problem? Please describe.

When working with @connection in a relational DataStore model, I find myself having to loop through the results and manually resolve the connection fields one by one whereas with API.graphql I don’t have to.

Fetching Posts with comments @connection for examples requires me to: . Fetch all the posts . loop through the posts and for each post fetch the comments

Given the simplicity of Datastore API, the fetching is not a big deal if you have one @connection, but once you have many it starts to feel cumbersome.

Describe the solution you’d like It would be cool if Datastore automatically resolves the @connections the way API.graphql works.

[iartemiev]

That’s correct, comments currently does not get populated. The docs specify retrieving them separately by passing in the related postID in the predicate.

We are currently working on a solution to retrieving related child items when querying a parent, so it will be possible to do in the near future.

[mdegrees]

@undefobj thank you