Zach Daniel

I like the proposed solution of doing it with `relationship_context` 👍 It also lends itself to a gradual migration, as we can first support both things but raise an error...

We want to use `Mix.shell()` to print, as opposed to `IO.puts`

Makes sense to add this, but I won't have time to do it for quite some time. What we ought to do is call the callback on returned data, and...

It would be less simple IMO not more simple to have a special route for simpler data layers, because often join resources end up getting behavior like fields/policies/actions.

👋 hey everyone, just checking in. Is this in progress? If so, any way I can assist? If not, I may be able to help get it off the ground...

Sounds good! Thanks for your hard work. Not trying to hurry. I'm happy to wait, just want to assist if possible/warranted.

Yeah, I'd be very happy to be involved in any way. Cross package search is a *major* win for the Ash ecosystem, and is absolutely worth me spending my time...

IIRC `result` will be `null` if `errors` is present, and `errors` will be `null` if the `result` is present, right? However, items in the error list being non null can...

Ah, yes you are right, we can definitely make that return type non nullable. Going from nullable -> not nullable on a returned type isn't breaking, so I'd definitely accept...

@barnabasJ does this solve the issue? https://github.com/ash-project/ash_graphql/pull/110