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
Retype's stale-work guard hardcoded options/multiple/currencyCode, so a request
carrying `precision` or `includeTime` against an already-correct type hit the
rename-only path and was silently discarded while reporting success — the exact
hand-listed-key bug this PR exists to remove. It reads TYPE_SPECIFIC_COLUMN_KEYS
now.
Filter values are read through the column that owns them. `parseScalar` returns
NaN for `50%`, `1h` and `$1,234.56`, so the value stayed a string, met the
numeric cast, and the range filter was rejected outright. Only cast columns take
this path — a text column keeps parseScalar's existing coercion and a select
keeps its option id verbatim.
CSV import was the one write path that bypassed `applyIncludeTime`, so an import
could put an instant into a column whose schema says it holds calendar days.
Decimal places is now clearable: the update sent nothing when the field was
emptied, so a precision could be set but never unset. `null` on the update
contract removes a key, applied in `updateColumnMetadata` and mirrored in the
optimistic cache. Non-finite input no longer clamps to 0 and saves as "zero
decimal places".
Filter pruning also moved off `type === 'select'` onto storesOpaqueIds /
storesMultipleValues, which the earlier sweep had missed.
Copy file name to clipboardExpand all lines: apps/sim/app/workspace/[workspaceId]/tables/[tableId]/components/column-config-sidebar/column-config-sidebar.tsx
+14-4Lines changed: 14 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -159,8 +159,15 @@ function ColumnConfigBody({
159
159
// type that loses it cannot leave a stale control behind.
0 commit comments