Extension: key analysis cache by workspace path for multi-root support
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- developer-experience
Research direction
Start in vscode-extension/src/commands/analyze.ts by tracing cachedAnalysis, pickWorkspacePath(), and getCachedAnalysis(). Then inspect its consumers in readiness.ts and instructions.ts. Done means analysis results are not reused across different workspace paths and both consumers receive the analysis for the selected root.
Written by the indexing model from the issue text.
Description
The extension's cachedAnalysis in vscode-extension/src/commands/analyze.ts is a single global variable. With pickWorkspacePath() enabling multi-root selection, if a user analyzes one folder then runs commands against a different folder, the cached analysis may be reused incorrectly (areas/apps from the wrong root).
Current: let cachedAnalysis: RepoAnalysis | undefined
Proposed: Map<string, RepoAnalysis> keyed by fsPath, with invalidation when the picked path differs from what's cached.
This affects getCachedAnalysis() consumers in:
vscode-extension/src/commands/readiness.tsvscode-extension/src/commands/instructions.ts
Ref: PR #55 review comments analyze.ts, readiness.ts
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 94
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 34
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 microsoft/agentrc
-
agentic-workflows automation readiness
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 25/100
microsoft/agentrc#379 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/agentrc#372 · 2 reactions ·
Maintainers usually reply within 1 day
-
[aw] Detection RunsOpenagentic-workflows
Difficulty 5/5 Over a week Newbie friendliness 1/100
microsoft/agentrc#349 · 8 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
All issues in microsoft/agentrc
Similar issues
-
security-scan
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
enhancement from-studio
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
esengine/DeepSeek-Reasonix#12048 · 1 comment ·
Maintainers usually reply within 1 day
-
fix(data-lake): land GitHub callback failures on the lake instead of the home page (epic #3813)Openbug data-lake github-integration UI/UX
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
test: pet colorsOpentestplan-item
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug claimable good first issue pillar/platforms
Difficulty 1/5 Under an hour Newbie friendliness 85/100
hurttlocker/o8#3277 ·
Maintainers usually reply within 1 day