New Table Change Cell Event issue

💬 App Building
2

Thank you for the feedback! These are both great points.

  1. This is a bug! I've filed this internally and we'll get it fixed in the next week or two.

  2. The way I've successfully set up background-save is to always flush the entire changeset when "Change Cell" is called, but I acknowledge that has other issues with concurrent saves. The lack of extra scope in the Event Handler is an intended short-term limitation as we decide what scope would be most valuable to include. We were hesitant to include currentRow and item because we weren't sure if / how they should include the changed value. I'd love to get your thoughts on what I'm currently thinking for extra scope:

currentSourceRow: Record<string, unknown>
// new property
event: { 
  newValue: unknown,
  oldValue: unknown,
  dataIndex: number,
  rowKey?: unknown 
}

We could bring the event variable to "Cell click" as well.