Does it make sense to use an input object as a parameter to a graphQL query(not mutation)

221 Views Asked by At

I am designing a graphQL service and looked at input objects and recommendations regarding using them for mutations. Does it also make sense to use input objects as parameter(s) to query if number of parameters is large(lets assume around 10 for the discussion)? Why? Why not?

Also, if it makes sense to use input objects for queries what should be considered to figure out if it is a right solution for me?

example query:

  retrieveData(
    ids: [ID!]
    codes: [String!]
    countries: [String!]
    types: [String!]
    business: [String!]
    locations: [ID!]
    region: Region!
    limit: Int = 50
    offset: Int = 0
    sortBy: SortBy
    version: Int
  ): Response!```
0

There are 0 best solutions below