Relationship with posts object as draft return null value which causes internal server error

[siddhantdante]

[jasonbahl]

I can confirm. Updating the field resolver to use DataLoader should resolve this.

Marking this actionable.

[dChiamp]

ran in to this today too on Version 0.4.0

[wf-ssahakyan]

Hi @jasonbahl, is it clear when this issue will be resolved? Thanks in advance

[jasonbahl]

I'm working on v0.6.0 right now and this is resolved in that.

It should be released this week or next week.

I'm going to close this issue as it's part of the v0.6 milestone and is addressed by the upcoming release.

[jasonbahl]

This is resolved by #262.

We can use the relationship field to set a relationship to a published post and a draft post, then query it as a public user and get no errors.

Here, we can see the relationship being set on the post edit screen:

Before

Querying for this field would return an error:

After:

Querying the relationship returns the public related nodes, but prevents the private (drafts, in this case) from being returned, and no errors are returned.

NOTE: The shape of the query has changed for relationship fields in this release. Relationship fields are now "connections" and the connected "nodes" are nested under the nodes field, as seen in the "after" screenshot.

[rodrigo-arias]

I'm glad this has been resolved. Do we have an ETA for release 0.6.0? I know it involves other updates

[arthay]

@jasonbahl hi. Do you have any news about Release v0.6.0? Thanks