Inbox: issue refs like #123 are styled but not linked in messages
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Read packages/ui/components/InlineMarkdown.tsx around lines 844–864 and packages/inbox/components/Thread.tsx around lines 133–159. Trace how the Inbox obtains each project's path and how Viewer receives repoInfo, then compare with code review and plan review. Done when bare issue references in Inbox messages link to the correct repository while other message rendering still works.
Written by the indexing model from the issue text.
Description
Bare issue refs in Inbox messages (for example #4236 in an agent's message about a GitHub repo) render in the link colour but aren't clickable.
InlineMarkdown only links #123 when it gets a repo through githubRepo / repoHost, otherwise it renders a styled <span>. The Inbox thread renders message bodies through Viewer without repoInfo, so every ref falls back to the span. Code review and plan review pass it, so refs link there.
- https://github.com/backnotprop/plannotator/blob/9f6132e/packages/ui/components/InlineMarkdown.tsx#L844-L864
- https://github.com/backnotprop/plannotator/blob/9f6132e/packages/inbox/components/Thread.tsx#L133-L159
The Inbox already knows each project's path, so it could resolve the git remote per project and pass it to Viewer as repoInfo.
Seen on plannotator 0.28.12, Linux, Claude Code.
- Dominant language
- TypeScript
- Stars
- 8.7k
- Forks
- 649
- Avg merge
- 2h 56m
- Merged PRs (30d)
- 294
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from backnotprop/plannotator
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
backnotprop/plannotator#1867 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
backnotprop/plannotator#1784 ·
Maintainers usually reply within 1 day
-
Claude Code: plan annotations are silently dropped when the plan is approved (approve path never sends feedback to the agent)Possibly taken @mangxy claimed this 42 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
backnotprop/plannotator#1359 ·
Maintainers usually reply within 1 day
-
Annotate documentation omits per-file version history and privacy controlsMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
backnotprop/plannotator#1086 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
backnotprop/plannotator#1069 ·
Maintainers usually reply within 1 day
All issues in backnotprop/plannotator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NaturalIntelligence/fast-xml-parser#890 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
zsviczian/obsidian-excalidraw-plugin#3000 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pnpm/get.pnpm.io#68 ·
-
[BUG] Cloudflare KV binding 模式下 kvDriver.list() 沿用 EdgeOne 语义，字段名不匹配导致 key 格式下初始化 500 并耗尽 list 配额Possibly taken @wumingzhinu claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
OpenListTeam/OpenList-Worker#125 ·
Maintainers usually reply within 2 days
-
Android (vision-camera-location): HybridLocationManager never quits its HandlerThread on disposeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
margelo/react-native-vision-camera#4217 ·
Maintainers usually reply within 4 days