You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(tables): stop insert-row flicker and return order_key from rows list
The rows insert flicker came from useCreateTableRow.onSettled invalidating
tableKeys.detail(tableId), which prefix-matches the nested rowsRoot rows query
and forces an un-cancelled refetch on every insert. A late offset refetch could
resolve after the optimistic splice and clobber freshly-inserted rows.
- invalidate detail with exact:true (+ lists) so the count surfaces refresh
without cascading into the rows query
- compare order keys bytewise in reconcileCreatedRow to match the server's
COLLATE "C" ordering and fitsAfter (was localeCompare)
- include order_key in the GET /rows list response; it was dropped in the
route mapping, so the client never saw keys and reconcileCreatedRow always
fell back to the position path
0 commit comments