Repository navigation
TBv3: concept panel fetches from the previous version after Back/Forward #2929
Description
After Back/Forward navigation, the concept detail panel on a repository page can fetch from the previous version. Example: open a versionless concept-panel URL (/<owner>/sources/<source>/concepts/<id>/), pick a released version from the version menu, then press Back. The panel requests …/<version>/concepts/<id>/$cascade/ against the version you just left.
Cause: during Back/Forward, RepoHome keeps the previous route's repo in state until the new one loads, and builds the panel URL from it. OpenConceptLab/oclweb3#68 fixed this race for the concept list: RepoHome now records the route each repository was fetched for (repoRoute) and renders Search only when that matches the current route. The panel isn't gated the same way.
Acceptance criteria
- After Back/Forward or a version change, the concept and mapping panels request only from the version the URL asks for.
Notes
- Probably small: gate
isPanelReady, or the panel URLs, on the sameisSameRepoScope(repoRoute, route)check that_canRenderSearchuses. - Check whether the panel shows the previous version's data or only makes one wasted request.
Activity
ocl-automation commentedon Oct 20, 2026
Automated Triage — 2026-10-20
Decision:
decision/ai-readyType:
type/bugSignals:
signal/quick-win,signal/low-risk,signal/small-scope,signal/well-specifiedThe issue names the cause (the panel URL is built from the stale
repoin RepoHome) and the likely fix: gateisPanelReadyor the panel URLs onisSameRepoScope(repoRoute, route), as #68 did for the concept list. That makes it a small change in a few files with one acceptance criterion; the open question of whether the panel shows stale data or only makes a wasted request is a code check. It builds on therepoRoutemechanism from #68 and is low risk because it is a front-end fetch-gating change.Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-5.5 (openrouter).