Philipinho dac65914ed chore(base): drop pre-virtualizer-fix scroll-jump workarounds ...

Two pieces of code added under the wrong height-mismatch theory of
the inline-embed scroll jump are no longer load-bearing now that the
real cause (virtual-core's _willUpdate calling _scrollToOffset(NaN))
is fixed by the initialOffset seed in grid-container.tsx:

  - BaseTableSkeleton's `rows` prop, whose only consumer was the
    "creating database" placeholder passing rows=0 to "match" the
    eventual empty-base height. Reverted to a fixed 10-row skeleton.
  - The Database slash command's React Query cache prefill of
    ["bases", id] and ["base-rows", id, …] (~30 lines), which
    existed to skip BaseTable's own loading skeleton on swap. The
    create endpoint return type is back to { id }.

The placeholder approach (pendingKey + setNodeMarkup patch) stays —
that's what gives the user visible state during the create request,
unrelated to the scroll jump.

2026-04-28 11:29:28 +01:00

..

client

chore(base): drop pre-virtualizer-fix scroll-jump workarounds

2026-04-28 11:29:28 +01:00

server

feat(base): seed inline-embed bases with two extra text columns and one row

2026-04-28 11:25:11 +01:00