Filter related doc fields in local API?

arielarial10 months ago

2

• 

  Payload-Bot11 months ago

  
  
  
• 

  justono11 months ago

  @736673642158620680

  I am just learning payload (v2) FYI so take it for what you will. I may have possibly encountered something that would help you. I think basically what you said with the afterRead hook would be a path forward. Just for some context, in my relationship field I'm sort of creating a computed display only field and I was querying assets assigned to an employee and in the end I was returning just the assets ID. I wonder if you just update where my map is in my afterRead hook that you could return any shape or limtied set of data that you would want.

  
  
  

  // Employees collection config
  ...
  {
     name: "assets",
     type: "relationship",
     relationTo: "assets",
     hooks: {
       afterRead: [getAllEmployeeAssets],
     },
  }]}
  
  const getAllEmployeeAssets: FieldHook = async ({ data }) => {
    // Use Local API to get the assets
    const allAssets = await payload.find({
      collection: "assets",
      where: {
        employee: {
          equals: data.id,
        },
      },
    });
    if (allAssets.docs) {
      // Map over and return anything you want (I'm just returning the id)
      return allAssets.docs.map((doc) => doc.id);
    }
  
    return null;
  };

  
  
  

  This blog post isn't SUPER realted but you could see how if you did end up making another field to hold a filtered set of data. Reacting to and updating other fields isn't too bad with their form hooks. Also I think this showcases a pretty interesting use case and also the power of the array field.

  https://payloadcms.com/blog/managing-array-and-block-rows
  
  

  You might be able to create and array of other fields then you get types etc cause everything is just fields instead of a JSON object. But depending on how complex you want go this seems like bit to manage where JSON field prolly is better.