René's URL Explorer Experiment


Title: improvement(data-drains): move drains to the fullscreen list/detail pattern by waleedlatif1 · Pull Request #5954 · simstudioai/sim · GitHub

Open Graph Title: improvement(data-drains): move drains to the fullscreen list/detail pattern by waleedlatif1 · Pull Request #5954 · simstudioai/sim

X Title: improvement(data-drains): move drains to the fullscreen list/detail pattern by waleedlatif1 · Pull Request #5954 · simstudioai/sim

Description: Summary Data drains was the last settings surface still on a Table + create modal. It now matches Skills and Custom Tools. List is SettingsResourceRow rows in a clickable button — source, destination, cadence, and last run on the row, plus a Disabled tag when a drain is paused. Clicking a row opens a detail sub-view with the drain's actions (Run now / Test connection / Delete), its enabled toggle, resolved destination config, and recent run history — replacing the expanding table row. Creating a drain is a fullscreen view instead of a ChipModal, reusing DESTINATION_FORM_REGISTRY so the two never fork. A drain is deep-linkable via data-drain-id (push to open, replace to close), matching custom-tool-id / custom-block-id. The detail is read-only apart from the enabled toggle — destination credentials are never returned by the API, so changing one means recreating the drain. Alignment work the migration surfaced: The destination registry rendered its 36 fields with ChipModalField, whose label is byte-identical to a SettingsSection header (text-small, --text-muted, pl-0.5) — on a page that made section titles and field labels indistinguishable. All of them, plus the create view's own fields, now use SettingRow like every other page-level detail view. The registry had exactly one consumer, so no modal was left behind. Shared source/destination/cadence label maps moved to labels.ts now that three files need them (verified byte-identical to the originals). Run status uses Badge with a dot instead of hand-coloured text, and byte counts use formatFileSize — the old /1024 math rendered a 5 GB export as 5242880.0 KB. Copy follows the sibling surfaces: Create drain (not New drain), Disabled (not Paused), Run queued, Connection test passed, No drains found matching …. Seed the list cache on create so landing on the new drain's detail doesn't depend on the invalidation refetch succeeding. Tradeoff worth a look Enable/disable and the per-row Run now / Test / Delete actions previously sat inline on each table row; they now live in the detail, so toggling several drains costs more clicks. That's inherent to the row pattern — a RowActionsMenu in the row's trailing slot would mean dropping the row-level