Support Providing Extra arguments from parent resolver to child resolver

[abishek-rz]

Hi I create some common context objects when resolving object in the root resolver, since I need to make an api call and prepare this context I don't want to repeat this call for every child resolver

The issue is when using query aliases the context from the last api call overrides all the query aliases, I would like to handle this by creating a query id when I'm at the root object and passing this as a additional query_id argument to all resolvers using extensions but It does not recursively pass from the parent to child resolver, could you please support this

[rafalp]

Root resolver returns data for top level query resolvers. It doesn't produce context.

To avoid repeating API calls you are supposed to cache your data on the context, but "having to repeat api call in child resolver" sounds like there's problem elsewhere. Usually child resolver shouldn't need to repeat parent's API call. Can you show the code?

[abishek-rz]

Thank you for this @rafalp This helps a lot
One more small question, Do I have to define the user class seperately or could I import it from the schema with

from ariadne import ObjectType
user = ObjectType("User")

[rafalp]

You'll have to use ObjectType to tell ariadne that resolve_user_fullname is for User's fullname field:

from ariadne import ObjectType

user = ObjectType("User")


@user.field("fullname")
def resolve_user_fullname(obj, _):
    return f"{obj.name} {obj.last_name}"

[abishek-rz]

I mean when declaring this

# this is example user resolver that returns user object with name and last name, but not full name
def resolve_user(...):
    return User(name="John", last_name="Doe")

[rafalp]

Ah. User class here is an example. It's up to you to decide how models are represented in your python logic. Everything is fine as long as it works for you.

[abishek-rz]

Thank you @rafalp