Custom Component Changes Not Enabling Save Draft or Publish Changes

58bits

3 months ago

2

• 

  alessiogr

  Payload Team

  2 months ago

  This is weird that that's required. Does that happen to every custom field or only with the lexical one?

• 

  58bits

  2 months ago

  Yeah - it was a puzzle for sure. And it only happens in our custom Lexical field FieldComponent and only (I believe) when it's part of a block field. I ran out of time trying to debug it - but I did test as much as I could including setting up a test repo, and at one point using the identical field definition, but with a swapped out field component (using a simpler component) and it worked. Heh. In the end

  setModified(true)

  just before

  setValue({...})

  worked fine and apparently without any other side effects and so I've left this as a future 'TODO: Revisit'.