UX-CAT-002 — Use consistent object-type icons
| Field | Value |
|---|---|
| Status | Open finding; source-verified and live-observed |
| Severity | Medium |
| Affected surface | Catalog and SQL Editor discovery trees |
| Implementation issue | oqullus #541 |
| Code-change repository | sparqd/oqullus |
Where the problem appears
Locate the same table, view, schema, and column in Catalog and SQL Editor and compare visible and accessible type indicators.
Concrete observed case
Catalog maps tables, views, schemas, and unknown objects to the same folder glyph. SQL Editor uses distinct table and column icons. The table type label may only become visible on hover.
Expected condition
Use one vocabulary: catalog/data source, schema/folder, table/grid, view-specific, and column icons. Always expose the object type in accessible text; hover may add detail but cannot be the only type cue.
Cause and evidence
- The same table receives different icons across the two surfaces.
- Catalog's folder mapping collapses several object types.
- Hover-only type information is unavailable to keyboard, touch, and quick scanning.
Why it matters
The hierarchy is misleading and users cannot reliably distinguish navigable containers from queryable relations.
Existing controls and workarounds
Check the hover label or SQL Editor representation when the Catalog icon is ambiguous.
Alternatives considered
- Recommended: shared typed icon mapping plus accessible labels.
- Text-only type badges — valid but visually heavier.
- Keep folder icons and rely on hover — rejected for accessibility and scanability.
Component involvement
- Oqullus owns the shared icon and accessibility vocabulary.
- BFF must preserve reliable relation types.
- Design validates light/dark themes and compact states.
Reproduction and verification
Follow CAT-S010. Record the visible state, request outcome, effective identity, and recovery behavior relevant to this finding.
Resolution conditions
Close when all supported object types have consistent visible and accessible treatment across Catalog and SQL Editor, including keyboard and touch use.
Validation and blockers
Oqullus, design, and accessibility owners must validate.