MapColonies / MapColonies/infra-tools

Sidebar tree of image references with scope toggle

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

Nobody has claimed this yet.

ready-for-agent
Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
22h 52m
Merged PRs (30d)
13

Description

## Parent

#17

## What to build

A view that surveys a file's image references instead of requiring a line-by-line read, and that can surface a broken reference in a file the developer does not have open.

By default it lists the active file's references with their status and follows the active editor. A toggle in the view's title bar switches to workspace scope, where the top level lists values files and **expanding one is what triggers its checks** — so a repository containing many charts stays usable, and widening scope does not fire hundreds of requests at once. Current-file is the default because a repository with many charts is the normal case here, not the exception.

Clicking an entry jumps to its line in the editor. Re-check is available at entry, file, and root level, so a fix can be confirmed without waiting for a cache entry to expire.

## Acceptance criteria

- [ ] The view lists the active file's references with their status and follows the active editor
- [ ] The title-bar toggle switches between current-file and workspace scope
- [ ] Workspace scope is off by default
- [ ] In workspace scope the tree lists values files without checking them
- [ ] Expanding a file is what triggers its references to be checked
- [ ] Clicking an entry reveals its line in the editor
- [ ] Re-check works at entry, file, and root level
- [ ] View and command registration tested through the shared editor stub

## Blocked by

- #21 — Checkmark decoration and hover for image reference results
- #24 — Chart context: file scope and `appVersion`-derived tags

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start with the view and command registration and the shared editor stub mentioned in the acceptance criteria, then review issues #21 and #24. Trace how the active editor and reference checks are represented before implementing the current-file default, workspace expansion behavior, navigation, and re-check actions. Done means all listed acceptance criteria pass through the shared editor stub.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.