Skip to content

fix(task-num): apply numPrefix to the dynamic-region task list (2nd render path) - #682

Merged
sonichi merged 1 commit into
mainfrom
fix/task-num-second-render-path
May 14, 2026
Merged

sonichi merged 1 commit into
mainfrom
fix/task-num-second-render-path

Conversation

@sonichi

@sonichi sonichi commented May 14, 2026

Copy link
Copy Markdown
Owner

Summary

PR #681 only patched the primary renderTasks at line 1148. The dashboard has a second task-list renderer at line 2280 (the dynamic-region contextual list) — that's the surface Chi was actually viewing. Hence "DevTools finds .task-text but text starts with '[Discord] '" — the 2nd renderer ran, no numPrefix.

This PR adds the same numPrefix logic to the 2nd renderer. .map() now passes (entry, i).

Why I missed it first time

Greped for task-num and task-text and patched the first match. Should have searched the full bundle for ALL displayText assignments before assuming one renderer.

Test plan

  • tsc clean
  • After merge + web-client kickstart + tab reopen: numbering appears on EVERY task in the dynamic-region list

🤖 Generated with Claude Code

…ender path)

#681 only patched the primary renderTasks (line 1148). There's a
SECOND renderer in the dynamic-region path (line 2280) for the
contextual task list — that's the one Chi was actually looking at.
Hence "I see 1. in querySelector but not in UI."

DevTools `textContent.slice(0,10)` on the visible list returned
'[Discord] ' — no numPrefix — confirming the second path was running.

This patch adds the same `var numPrefix = (i + 1) + '. ';` +
`displayText = numPrefix + ...` to the second renderer. .map() now
passes (entry, i) so i is available.
@sonichi
sonichi merged commit 50a5358 into main May 14, 2026
1 check passed
@sonichi
sonichi deleted the fix/task-num-second-render-path branch May 14, 2026 02:21
liususan091219 pushed a commit to liususan091219/sutando-fork that referenced this pull request May 28, 2026
…ender path) (sonichi#682)

sonichi#681 only patched the primary renderTasks (line 1148). There's a
SECOND renderer in the dynamic-region path (line 2280) for the
contextual task list — that's the one Chi was actually looking at.
Hence "I see 1. in querySelector but not in UI."

DevTools `textContent.slice(0,10)` on the visible list returned
'[Discord] ' — no numPrefix — confirming the second path was running.

This patch adds the same `var numPrefix = (i + 1) + '. ';` +
`displayText = numPrefix + ...` to the second renderer. .map() now
passes (entry, i) so i is available.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant