Determining if record exists in `condition` (condition has no access to `data.id`)

ssyberg

5 months ago

42

• 

  notchr

  5 months ago

  @ssyberg How are you writing the condition? Can you explain a little more in detail please? 🙂

• 

  ssyberg

  5 months ago

  Sure I just verified this in a fresh install, here's the collection (just a slight modification of the Example collection

  
  

  
  

  import { CollectionConfig } from 'payload/types';
  
  // Example Collection - For reference only, this must be added to payload.config.ts to be used.
  const Examples: CollectionConfig = {
      slug: 'examples',
      admin: {
          useAsTitle: 'someField',
      },
      fields: [
          {
              name: 'foo',
              type: 'text',
          },
          {
              name: 'someField',
              type: 'text',
              admin: {
                  condition: (data, _) => {
                      if (data && data.id) {
                          return true;
                      } else {
                          console.log('Hide it!');
                          return false;
                      }
                  },
              },
          },
      ],
  };
  
  export default Examples;

• 

  notchr

  5 months ago

  Hmm

  
  

  
  

  I think I'm confused hehe, do you mean hide the collection if there is no data?

  
  

  
  

  Or hide the field?

• 

  ssyberg

  5 months ago

  Hide the field

• 

  notchr

  5 months ago

  Ahh

  
  

  
  

  Well you can override the default ID field, though I'm not sure if that will then be available?

  
  

  
  

  https://payloadcms.com/docs/fields/overview#customizable-id
  

  
  

  Collections ID fields are generated automatically by default. An explicit id field can be declared in the fields array to override this behavior. Users are then required to provide a custom ID value when creating a record through the Admin UI or API. Valid ID types are number and text.
• 

  ssyberg

  5 months ago

  Hmm not sure if that helps

• 

  notchr

  5 months ago

  Could that be a solution?

  
  

  
  

  hmm

• 

  ssyberg

  5 months ago

  I'm happy with the id field as is, I just want to access it in the condition callback

• 

  notchr

  5 months ago

  Right, but it doesn't exist until published right?

• 

  ssyberg

  5 months ago

  Correct! That's exactly what I want to leverage!

• 

  notchr

  5 months ago

  Then the condition check is accurate then

  
  

  
  

  right?

• 

  ssyberg

  5 months ago

  Yes, for the pre-create state it's perfect

  
  

  
  

  But after record creation, there is still no

  id

  available in the condition callback

• 

  notchr

  5 months ago

  Ahhhh

• 

  ssyberg

  5 months ago

  A silly workaround would be to populate a hidden field during a create hook, but that really seems non-ideal

• 

  notchr

  5 months ago

  What did data log?

  
  

  
  

  in the condition cb

• 

  ssyberg

  5 months ago

  data log shows all the data... except the id 😂

  
  

  
  

  This is in a different context, but here's an example of the data object after create:

  
  

  {
      "blogs": 0,
      "_status": "draft",
      "programs": 0,
      "projects": 0,
      "hero": {},
      "meta": {},
      "streamContained": 0,
      "supplementalLinks": 0
  }

  
  

  
  

  Now here's where it gets even weirder

• 

  notchr

  5 months ago

  How about siblingData?

• 

  ssyberg

  5 months ago

  I'm seeing multiple calls to the condition callback on render, 7 in this case. The first one has the id! But none of the subsequent ones do.

  
  

  
  

  siblingData

  is no different

  
  

  
  

  Possible this is actually a bug?

• 

  notchr

  5 months ago

  well not sure if it's a bug, but maybe an oversight

  
  

  
  

  The weird thing is that the first one has ID

  
  

  
  

  condition will run once for every field IIRC

  
  

  
  

  in my test case, the first two logs return the id

  
  

  
  

  wait jk only the first one

  
  

  
  

  yeah this might be a bug

  
  

  
  

  @ssyberg I'd make an issue on GH

• 

  ssyberg

  5 months ago

  Ok will do!

  
  

  
  

  condition will run once for every field IIRC
  

  I wonder why I'm seeing it run so many times for a single field

  
  

  
  

  https://github.com/payloadcms/payload/issues/2524