feat(ui): nested scope-stack breadcrumb and a breadcrumb in single-definition view
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start with web/src/lib/components/browse/SourcePane.svelte around line 333, where the breadcrumb calls innermostSymbolAt; change it to list every enclosing symbol instead of only the innermost one. For the single-definition view, offset line lookups from node.startLine. Done means a three-level fixture renders the full stack and the existing breadcrumb live check is updated to match.
Written by the indexing model from the issue text.
Description
What exists today?
The source pane's breadcrumb (BRW-10).
How does it behave now?
It shows only the innermost enclosing symbol at the first visible line (innermostSymbolAt). The single-definition view has no breadcrumb.
How should it behave?
Show every enclosing symbol (for example type Foo › method Bar › closure). In single-definition view, offset from node.startLine, so a long type body names the method being read.
What kind of improvement?
Output clarity or formatting
Would this change existing behavior?
UI only; no wire change expected.
Evidence
web/src/lib/components/browse/SourcePane.svelte:333
Acceptance criteria
- The nested stack renders correctly on a fixture with three nesting levels; the existing breadcrumb live check is updated.
Source (GSD planning files, archived at d384473e): .planning/milestones/v0.13.0-REQUIREMENTS.md:82 (BRW-14); .planning/milestones/v0.13.0-phases/09-source-view-follow-through-breadcrumb-editor-handoff/09-CONTEXT.md (Deferred Ideas)
🤖 Generated with Claude Code
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- Avg merge
- 5h 16m
- Merged PRs (30d)
- 107
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 seanb4t/codegraph-go
-
area:indexer bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#385 ·
Maintainers usually reply within 1 day
-
chore needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
seanb4t/codegraph-go#380 ·
Maintainers usually reply within 1 day
-
chore needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#379 ·
Maintainers usually reply within 1 day
-
chore needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
seanb4t/codegraph-go#362 ·
Maintainers usually reply within 1 day
-
area:query bug priority:low spec-needed
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
seanb4t/codegraph-go#355 ·
Maintainers usually reply within 1 day
All issues in seanb4t/codegraph-go
Similar issues
-
enhancement exporter/awskinesis needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
open-telemetry/opentelemetry-collector-contrib#53334 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
erigontech/erigon#26523 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
SocialGouv/iterion#3376 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
seaweedfs/seaweedfs#12740 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day