feat(ui): nested scope-stack breadcrumb and a breadcrumb in single-definition view

Open
#118 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
frontend

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

area:ui enhancement priority:low spec-needed
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

https://claude.ai/code/session_01UNqdnC3q6U362BvyfxuKCF

Dominant language
Go
Stars
0
Forks
0
Avg merge
5h 16m
Merged PRs (30d)
107

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from seanb4t/codegraph-go

All issues in seanb4t/codegraph-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.