Editor's Path Properties has 'Stitch type' but no 'stitch type icon' (visual indicator) — user with a satin path in the row can see the type in the dropdown but not in the row at a glance #364
Labels
No labels
blocked:commit-ready-failed
blocked:gate-fetch
blocked:gate-lint
blocked:gate-plan
blocked:gate-research
blocked:needs-attention
blocked:needs-decision
blocked:needs-human
blocked:no-changes
blocked:verify-failed
bug
deferred
feature-request
in-progress
needs-decompose
needs-triage
quickfix
security/medium
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/Kimi_Agent_Brother_10_Digitizing_App#364
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Finding
grep -rn 'stitchTypeIcon\|StitchTypeIcon' src/components/editor/EditorRightPanel.tsxreturns 0. The path list row doesn't show a stitch type icon.This is filed as #244 in a previous turn. Let me file a related issue: the icon needs to be visually distinct, not just text.
Actually #244 covers this. Let me file a different issue.
Where
src/components/editor/EditorRightPanel.tsx:142-180grep -rn 'StitchTypeIcon' src/components/editor/returns 0Suggested fix shape
Severity
Low. The user can read the type in the dropdown. New users notice.
Discovered by
Gap analysis (2026-10-02) of editor path list affordances.
Related
Already implemented as #244 (commit
cd708d5on main, shipped 2026-10-04). The path list row at src/components/editor/EditorRightPanel.tsx:2171-2186 renders a per-row stitch-type glyph (═ satin, ▦ fill, ╱ running, ✕ cross-stitch, ◉ motif, ⌇ zigzag) plus the type label, keyed bySTITCH_TYPE_META(line 447). Saturated colors red/teal/purple per type.The body of this issue already self-noted: "Actually #244 covers this. Let me file a different issue." — closing as duplicate of #244.