Select options without GraphQL name validation

p.tek

3 months ago

6

• 

  jarrod69420

  3 months ago

  You could probably set the labels to your "00:00" format and adjust the values of the options to something usable by graphql enums

  
  

  
  

  [{ label: '00:00', value: '00_00' }]

• 

  p.tek

  3 months ago

  Thank you for the suggestion! The value has to start with an underscore or a letter as well as using no special characters, e.g. 'T00_00', and the client(s) would have to reformat this to the real value before use (or use a lookup table).

  
  
  

  So far, I have reverted to using a text field with a format validation. Hoping Payload will support "lenient select" before I get around to implementing a custom field / component combo 🙂

• 

  jarrod69420

  3 months ago

  I don’t think we will because we use enums for the select field in GraphQL so we are bound to the restrictions that come with it

  
  

  
  

  You could wire up an after read hook so the value gets altered before getting to the client though

• 

  p.tek

  3 months ago

  That worked well. I'll use the after read hook as you suggested. Thank you!
  
  

  Edit: Unfortunately, I spoke too soon. It worked when testing on a draft document for a versioned collection, but as soon as I tried to publish, a frontend validation error was triggered in the admin UI.

  
  
  

  I'll stick with the text field for now. Thank you anyway.