Package v0.2.12→v0.2.124: manifest, actions, version graph

startos/versions/v0.2.46.ts

@@ -0,0 +1,13 @@
+import { VersionInfo } from '@start9labs/start-sdk'
+
+export const v_0_2_46 = VersionInfo.of({
+  version: '0.2.46:0',
+  releaseNotes: {
+    en_US:
+      'Drag-reorder now works for newly-added columns. Root cause (finally found via the v0.2.44 diagnostic logging): currentOrderedKeys() was returning state.jobsColumnOrder directly — the saved order from localStorage. But applyColumnPrefs renders columns in saved-order-FIRST + new-catalog-keys-APPENDED order, so a relay update that added new columns (e.g. download_ms, transcribe_ms_sum, analyze_wall_time_ms) showed them in the table but they were NOT in the saved order. When the user dragged one of those new columns, indexOf(dragKey) returned -1, the splice short-circuited, and the column visibly snapped back. Fixed: currentOrderedKeys() now reads from the DOM (.jobs-table th[data-col]) — what applyColumnPrefs already computed and rendered, which always reflects the FULL current order including appended new catalog keys. Once the user successfully drags a new column, the now-complete order gets saved to localStorage and subsequent drags work naturally. Also removed the [drag] diagnostic console.log statements added in v0.2.44 since they\'ve served their purpose.',
+  },
+  migrations: {
+    up: async ({ effects }) => {},
+    down: async ({ effects }) => {},
+  },
+})