How to access parent input argument from child data fetcher

[driptaroop]

I have a graphQL schema,

type Query {
    getContact (customerId: ID!): Contact
}

type Contact {
    email: String
    address: [Address]
}

type Address {
    street: String!
    number: String!
    additional: String
    pincode: String!
    city: String!
    country: String!
}

I generated the data models using the codegen plugin and wrote 2 data fetchers (contact and address). In the contact data fetcher, I can access the customerId using @InputArgument annotation. I am not able to access the customerId in the address data fetcher. I tried using @InputArgument (which getting null). Also, I tried DataFetchingEnvironment.arguments which is also resolving as an empty map.

code:

@DgsComponent
class ContactFetcher(
    private val addressService: AddressService
) {
    @DgsData(parentType = DgsConstants.QUERY_TYPE, field = DgsConstants.QUERY.GetContact)
    fun contact(@InputArgument("customerId") customerId: String): Contact = 
        Contact(email = "[email protected]") // here I can access the customerId

    @DgsData(parentType = DgsConstants.CONTACT.TYPE_NAME, field = DgsConstants.CONTACT.Address)
    fun address(dfe: DataFetchingEnvironment): List<Address> {
       /* I need to fetch the address based on the customer Id. but how to access customerId here?
          I tried dfe.arguments which is an empty map. @InputArgument does not work also.*/
        return addressService.getAddresses(customerId) 
    }
}

[paulbakker]

What you're likely looking for is the getSource method on DataFetchingEnvironment. This would give you the Contact in the address fetcher.

[paulbakker]

I added another reply to that thread yesterday which is seems to be the answer to exactly what you're asking: #21 (reply in thread)

Make sure to read the reply after the one linked as well, I've added a link to an example there.

[srinivasankavitha]

The input argument to the query is also available in the DataFetchingEnvironment's operationDefinition field that you can access like this:

// This gives you the first field that was selected on the query
Field result = (Field)(dfe.getOperationDefinition().getSelectionSet().getSelections().get(0));
// This gives you the first argument's value and so on
result.getArguments().get(0).getValue();

Admittedly, this is jumping through some hoops to get the value, so ultimately depends on what is convenient for you.

[driptaroop]

Thank you @paulbakker . I replied in the other thread.

Thank you @srinivasankavitha as well. I indeed got the value by this way although this is a very verbose way of getting it. A more intuitive way of getting the root arguments would make the usage a bit easier. I am thinking some annotation based method parameter injection (something like @RootArguments, working similarly as @InputArgument but for root arguments). Is there something like this on the feature roadmap for DGS since this might be a common use case?

[yamalameyooooo]

// This gives you the first field that was selected on the query
Field result = (Field)(dfe.getOperationDefinition().getSelectionSet().getSelections().get(0));
// This gives you the first argument's value and so on
result.getArguments().get(0).getValue();

@srinivasankavitha i have got the similar use case, but in my case there are 4 argument and they can be given in any order, so managing them in code is tedious, can we have the same suggestion to get the values by argument names instead of getting it from list by index? as i may never know in 0th place what value for which argument is present

[srinivasankavitha]

That's hard to determine since this is basically using the API exposed by graphql-java. I would recommend having a deterministic order for the arguments that you can use to extract.

[srinivasankavitha]

That is a great suggestion since this is a common use case. We will add this to the roadmap.

…

On Sun, Feb 7, 2021 at 9:41 AM Driptaroop Das ***@***.***> wrote: Thank you @paulbakker <https://github.com/paulbakker> . I replied in the other thread. Thank you @srinivasankavitha <https://github.com/srinivasankavitha> as well. I indeed got the value by this way although this is a very verbose way of getting it. A more intuitive way of getting the root arguments would make the usage a bit easier. I am thinking some annotation based method parameter injection (something like @RootArguments, working similarly as @InputArgument but for root arguments). Is there something like this on the feature roadmap for DGS since this might be a common use case? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#23 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJ5JPXLWBZXMH34OZDJWYXDS53GGFANCNFSM4XDYBNWA> .

[srinivasankavitha]

Created a new issue for this - #36

[driptaroop]

Great! I will resolve this discussion. 👍🏼