Editor has no 'node count goal' or 'simplification suggestion' — user with 200 nodes wanting to know 'is this too many?' has no rule of thumb surfaced #326

New issue

Closed

opened 2026-10-04 03:52:30 +00:00 by Mark · 1 comment

Mark commented

2026-10-04 03:52:30 +00:00

Owner

Finding

grep -rn 'nodeCountGoal\|tooManyNodes' src/components/editor/ returns 0. The editor has no node count guidance.

A user with 200 nodes in a satin column:

Doesn't know if that's "a lot" or "normal"
The Help page might have a rule of thumb
The editor doesn't show it

The fix is a small "Node count: 200 (consider simplifying)" hint when the count exceeds a threshold.

Where

Path Properties: src/components/editor/EditorRightPanel.tsx (per the snippet)
No guidance: grep -rn 'tooManyNodes' src/components/editor/ returns 0
The node count: per p.nodes.length

Suggested fix shape

UI: in the Path Properties section, near the node count display:

{p.nodes.length > 50 && (
  <p className="text-[10px]" style={{ color: '#E6A948' }}>
    💡 200 nodes is more than typical (10-30). Consider simplifying.
  </p>
)}

Threshold: 50 nodes is the threshold for "consider simplifying." 100+ is "definitely too many."
Tooltip: a longer explanation on hover: "Satin columns typically have 10-30 nodes for clean curves. More nodes may cause jagged rendering and slower export."
Action: a "Simplify" button next to the hint (per #279).
Use cases: the user can see at a glance if their path is over-detailed.

Severity

Low. The user can render and see. Power users notice.

Discovered by

Gap analysis (2026-10-02) of editor guidance.

#270 (open) — Node count. The count is shown; the guidance is the addition.
#279 (open) — Simplify. The action is the response to "too many nodes."
Figma's "Simplify paths" hint is the parallel.

## Finding `grep -rn 'nodeCountGoal\|tooManyNodes' src/components/editor/` returns 0. The editor has no node count guidance. A user with 200 nodes in a satin column: - Doesn't know if that's "a lot" or "normal" - The Help page might have a rule of thumb - The editor doesn't show it The fix is a small "Node count: 200 (consider simplifying)" hint when the count exceeds a threshold. ## Where - Path Properties: `src/components/editor/EditorRightPanel.tsx` (per the snippet) - No guidance: `grep -rn 'tooManyNodes' src/components/editor/` returns 0 - The node count: per `p.nodes.length` ## Suggested fix shape 1. **UI**: in the Path Properties section, near the node count display: ```tsx {p.nodes.length > 50 && ( <p className="text-[10px]" style={{ color: '#E6A948' }}> 💡 200 nodes is more than typical (10-30). Consider simplifying. </p> )} ``` 2. **Threshold**: 50 nodes is the threshold for "consider simplifying." 100+ is "definitely too many." 3. **Tooltip**: a longer explanation on hover: "Satin columns typically have 10-30 nodes for clean curves. More nodes may cause jagged rendering and slower export." 4. **Action**: a "Simplify" button next to the hint (per #279). 5. **Use cases**: the user can see at a glance if their path is over-detailed. ## Severity Low. The user can render and see. Power users notice. ## Discovered by Gap analysis (2026-10-02) of editor guidance. ## Related - #270 (open) — Node count. The count is shown; the guidance is the addition. - #279 (open) — Simplify. The action is the response to "too many nodes." - Figma's "Simplify paths" hint is the parallel.

Mark added the

feature-request

triage-approved

labels

2026-10-04 03:52:30 +00:00

Mark referenced this issue

2026-10-04 03:53:55 +00:00

Editor's Path Properties section has no 'spike' / 'sharp corner' detection — user creating a path with a sharp angle (e.g., a 10° corner) gets no warning, embroidery on sharp corners is hard #335

Mark referenced this issue

2026-10-04 03:56:29 +00:00

Editor's stitch type dropdown doesn't surface which types are appropriate for the path's geometry — user picking 'fill' for a 2-node line gets no warning (fill is meaningless for a line) #354

Mark referenced this issue

2026-10-04 04:01:21 +00:00

Editor's Path Properties has 'Stitch type' but no 'recommended stitch type' for the path's geometry — user with a 2-node line gets a 'Satin' option (which is unusual for a line) #385

Mark referenced this issue from a commit

2026-10-05 01:32:52 +00:00

fix(#326): editor 'Total Nodes' surfaces a simplification nudge at 50+/100+ thresholds

Mark commented

2026-10-05 01:33:14 +00:00

Author

Owner

Shipped in commit 56ccc5e (pushed to main).

Adds a hint in the Path Properties panel, immediately below the Total Nodes row:

50..99 nodes → amber "💡 N nodes is more than typical (10-30). Consider simplifying."
≥100 nodes → red "⚠ N nodes is a lot — definitely too many. Consider simplifying."
Hover tooltip: explains the satin-column 10-30 rule + mentions the Simplify action.

The Simplify button (#279) already lives right below, so the hint is immediately actionable.

8 new tests in src/components/editor/issue-326.test.tsx cover the threshold boundaries (49/50/75/100/200), the color/copy split, the tooltip, and the no-path-selected case. 211 existing EditorRightPanel tests still pass. The 3 failures in src/components/workspace/issue-275.test.tsx are pre-existing on main (verified with git stash + rerun) — unrelated to this change.

Closes #326.

Shipped in commit 56ccc5e (pushed to main). Adds a hint in the Path Properties panel, immediately below the Total Nodes row: - 50..99 nodes → amber "💡 N nodes is more than typical (10-30). Consider simplifying." - ≥100 nodes → red "⚠ N nodes is a lot — definitely too many. Consider simplifying." - Hover tooltip: explains the satin-column 10-30 rule + mentions the Simplify action. The Simplify button (#279) already lives right below, so the hint is immediately actionable. 8 new tests in `src/components/editor/issue-326.test.tsx` cover the threshold boundaries (49/50/75/100/200), the color/copy split, the tooltip, and the no-path-selected case. 211 existing EditorRightPanel tests still pass. The 3 failures in `src/components/workspace/issue-275.test.tsx` are pre-existing on main (verified with `git stash` + rerun) — unrelated to this change. Closes #326.

Mark closed this issue

2026-10-05 01:33:17 +00:00