PLU-818: [TILES-ATOMIC-INCREMENT-2] use .data() to automically update nested objects

[pregnantboy]

TL;DR

Introduced a new patchTableRow function to atomically update specific columns in a table row while preserving other columns

What changed?

• Currently, the update row action fetches the old data, merges the new changes and writes back.
• This new implementation uses .data() to patch nested keys.

How to test?

1. Create a table row with multiple columns
2. Update only specific columns using the update-row action
3. Verify that:
   • Only specified columns are updated
   • Non-existent columns are ignored
   • Other column values remain unchanged
   • Updates to non-existent rows fail gracefully
   • Number strings are automatically marshalled correctly

Why make this change?

The previous implementation required fetching the entire row before updating it, which could lead to race conditions and unnecessary data reads. The new atomic patch operation is more efficient and safer, as it updates only the specified columns in a single operation while preserving existing data.

[pregnantboy]

• PLU-309: [TILES-ATOMIC-INCREMENT-4] backend implementation for increment/decrement row value #835
• PLU-309: [TILES-ATOMIC-INCREMENT-3] enhance multirow-multicol UI with custom styles and operators #819
• PLU-818: [TILES-ATOMIC-INCREMENT-2] use .data() to automically update nested objects #818 👈 (View in Graphite)
• PLU-817: [TILES-ATOMIC-INCREMENT-1] allowing copying of row id in tiles #817
• develop-v2

This stack of pull requests is managed by Graphite. Learn more about stacking.

[kevinkim-ogp]

lgtm, tested that update-row is working as expected 💪

[pregnantboy]

Merge activity

• Dec 19, 2:02 AM EST: A user started a stack merge that includes this pull request via Graphite.
• Dec 19, 2:02 AM EST: A user merged this pull request with Graphite.