Feat/customizable result colors#354
Conversation
…lds, using the selected theme’s colors by default.
| ); | ||
| return; | ||
| } | ||
| if ( |
There was a problem hiding this comment.
WARNING: PK check is nested inside the columnMetadata conditional
The primary-key presence check is inside the if (columnMetadata && columnMetadata.length > 0) block. When columnMetadata is unavailable (e.g., some drivers don't provide result metadata), this check is skipped entirely. Users experience the old silent-failure behavior instead of the helpful alert added by this PR.
The PK check depends only on pkColumn and columns, both of which are always available. Move it outside the columnMetadata block so it runs consistently for all existing rows.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| const t = columnType.toLowerCase(); | ||
| if (/bool|^bit/.test(t)) return "boolean"; | ||
| if (/date|time|timestamp|year/.test(t)) return "date"; | ||
| if (/int|serial|float|double|decimal|numeric|real|money|number|fixed/.test(t)) |
There was a problem hiding this comment.
WARNING: Number type regex matches non-numeric types
The regex /int|serial|float|double|decimal|numeric|real|money|number|fixed/ matches any substring, so PostgreSQL types like interval and inet are incorrectly colored as numbers.
Use a stricter pattern with word boundaries to avoid matching substrings:
| if (/int|serial|float|double|decimal|numeric|real|money|number|fixed/.test(t)) | |
| if (/\bint(?:eger)?(?:\d+)?\b|serial|float|double|decimal|numeric|real|money|number|fixed/.test(t)) |
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| "date": "Date / Time", | ||
| "boolean": "Boolean", | ||
| "reset": "Reset to theme", | ||
| "custom": "Custom", |
There was a problem hiding this comment.
SUGGESTION: Unused i18n key
The "custom" key is not referenced anywhere in ResultColorsSection.tsx. Consider removing it to keep translations clean.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| "boolean": "Boolean", | ||
| "reset": "Reset to theme", | ||
| "custom": "Custom", | ||
| "previewLabel": "Preview", |
There was a problem hiding this comment.
SUGGESTION: Unused i18n key
The "previewLabel" key is not referenced anywhere in ResultColorsSection.tsx. Consider removing it to keep translations clean.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| ); | ||
| return; | ||
| } | ||
| if ( |
There was a problem hiding this comment.
WARNING: PK check is nested inside the columnMetadata conditional
The primary-key presence check is inside the if (columnMetadata && columnMetadata.length > 0) block. When columnMetadata is unavailable (e.g., some drivers don't provide result metadata), this check is skipped entirely. Users experience the old silent-failure behavior instead of the helpful alert added by this PR.
The PK check depends only on pkColumn and columns, both of which are always available. Move it outside the columnMetadata block so it runs consistently for all existing rows.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| "date": "Date / Time", | ||
| "boolean": "Boolean", | ||
| "reset": "Reset to theme", | ||
| "custom": "Custom", |
There was a problem hiding this comment.
SUGGESTION: Unused i18n key
The "custom" key is not referenced anywhere in ResultColorsSection.tsx. Consider removing it to keep translations clean.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| "boolean": "Boolean", | ||
| "reset": "Reset to theme", | ||
| "custom": "Custom", | ||
| "previewLabel": "Preview", |
There was a problem hiding this comment.
SUGGESTION: Unused i18n key
The "previewLabel" key is not referenced anywhere in ResultColorsSection.tsx. Consider removing it to keep translations clean.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: No Issues Found | Recommendation: Merge All issues from the previous review have been resolved in the latest commits:
Files Reviewed (3 incremental + 14 unchanged)Changed (all issues fixed):
Unchanged (no issues):
Previous Review Summary (commit f664cd8)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit f664cd8)Status: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (14 files)
Reviewed by kimi-k2.6-20260420 · Input: 46.6K · Output: 6.5K · Cached: 111.1K |
Code Review SummaryStatus: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (14 files)
|
Co-authored-by: kilo-code-bot[bot] <240665456+kilo-code-bot[bot]@users.noreply.github.com>
…egex, drop unused i18n keys
This PR adds two improvements to the data experience:
(numbers, text, dates, booleans) instead of rendering everything in a
single color.
make editing single-table SELECT results reliable.
1. Result colors by data type
You can now colorize query result cells based on their data type, with full
control over the colors.
before).
preview and a "Reset to theme" button per type.
in the app config and applied on top of any theme.
and NULL keep their existing styling.
2. Editing improvements
Save with Cmd/Ctrl+S
save_grid_changesshortcut commits the active tab's pending changes,like TablePlus. It's rebindable and listed under Settings → Keyboard
Shortcuts.
Editable single-table SELECT results
before building the UPDATE.
with a cryptic
1054 Unknown columnerror.guidance to include it (needed for a safe
WHEREclause).views) remain read-only, as before.