Why does relationship return null in a custom GraphQL query?

noheadphones

last month

20

{
  "data": {
    "GetCustomerOrders": {
      "docs": [
        {
          "id": "63edd88930491a91de039454",
          "createdAt": "2023-02-16T07:17:29.488Z",
          "paid": true,
          "product": null,
          "amount": 24000,
          "status": "IN_PROGRESS"
        }
      ]
    }
  }
}

const orders = await payload.find({
    collection: 'orders',
    depth: 3,
    limit: 100,
    sort: '-createdAt',
    where: {
      'customer.value': {
        equals: customer.id,
      },
    },
    overrideAccess: true,
  })

  console.log('orders', orders.docs)

  return orders

export const GetCustomerOrders = (GraphQL: typeof ImportedGraphQL, payload: Payload) => {
  return {
    args: {},
    resolve: GetCustomerOrdersResolver,
    type: buildPaginatedListType('CustomerOrders', payload.collections['orders'].graphQL?.type),
  }
}

product: { value: [Object], relationTo: 'products' },

query {
  GetCustomerOrders {
    docs {
      id
      createdAt
      paid
    product {
      value {
        ... on Product {
          title
        }
      }
    }
    amount
    status
    }
  }
}

• 

  jmikrut

  Payload Team

  4 weeks ago

  so

  
  

  
  

  i am guessing this is because even though you are using the local API for your top-level query, and passing

  overrideAccess: true

  , you are still using the default

  orders

  GraphQL type that Payload builds

  
  

  
  

  and when you are querying on the field

  product

  , that is actually using Payload's internal GraphQL population method for retrieving the

  product

  field

  
  

  
  

  and that internal population method

  requires authentication
  

  
  

  basically even if your top-level resolver returns that data, because you are using an internal Payload GraphQL type, GraphQL will use

  Payload's internal field resolvers for relationship fields, requiring authentication
• 

  noheadphones

  4 weeks ago

  Interesting, the request is via authentication only. I basically want to recreate the generated "get orders" query but instead of having to pass a customer id into the query, I retrieve it from the req object so that 1. devex is easier and 2. theres no way to accidentally query other customer's orders even though in theory access control should handle that

  
  
  

  the product in this case is publically readable as well, i get customer id from req object and check a few details and then return the orders

  
  

  
  

  this is the full resolver

  
  

  interface ResolverArgs {}
  
  export const GetCustomerOrdersResolver = async (obj, args: ResolverArgs, { req }, info) => {
    const customer = req.user
  
    if (!customer.id) {
      throw new Error('Invalid user id')
    }
  
    if (customer.collection !== 'customers' || !customer._verified) {
      throw new Error('User could not be verified.')
    }
  
    const orders = await payload.find({
      collection: 'orders',
      depth: 3,
      limit: 100,
      sort: '-createdAt',
      where: {
        'customer.value': {
          equals: customer.id,
        },
      },
      overrideAccess: true,
    })
  
    return orders
  }

  
  

  
  

  but like you say it sounds like the resolver is not the issue

  
  

  
  

  in my request in the playground i'm passing a valid jwt token

  
  

  
  

  so when you say

  
  
  

  Payload's internal field resolvers for relationship fields, requiring authentication
  

  
  

  I played around with this more to try and figure it out but unfortunately I'm still stuck, @jmikrut any ideas for a solution?

• 

  jmikrut

  Payload Team

  4 weeks ago

  you should try passing the

  req

  or the

  user

  through to your

  payload.find
  

  
  

  it's still the resolver for sure. basically, you're saying give me orders with

  depth: 3
  

  
  

  but in reality, GraphQL doesn't care about if you ask for

  depth: 3

  or not, because it will handle population for each relationship itself

  
  

  
  

  so you should only do

  depth: 0

  there

  
  

  
  

  and let GraphQL handle the populations that you need for you via the built-in resolvers

  
  

  
  

  it may be due to

  depth: 3

  actually

• 

  noheadphones

  4 weeks ago

  🤦

  
  

  
  

  that was totally it, thanks a lot for the explanation

  
  

  
  

  the whole context ^ helps a lot for future issues as well