Skip to content

feat: implement VSCode-based project detection and tool filtering#61

Open
suung wants to merge 3 commits into
mainfrom
60-project-dependent-tool-selection
Open

feat: implement VSCode-based project detection and tool filtering#61
suung wants to merge 3 commits into
mainfrom
60-project-dependent-tool-selection

Conversation

@suung
Copy link
Copy Markdown
Collaborator

@suung suung commented Oct 3, 2025

  • Add ProjectDetector using VSCode APIs for language detection
  • Enhance ToolsTreeProvider with project-aware tool filtering
  • Add VSCode commands: 'Detect Project Languages' and 'Export Project Info for CLI'
  • Implement tool compatibility indicators (✓ Compatible / ⚠ Not compatible)
  • Add comprehensive e2e tests for project detection system
  • Clean API for VSCode to CLI data passing via .carbonara-project-info.json

Resolves #60 - Project dependent tool selection

run the e2tests to verify

@suung suung added this to the November Release milestone Oct 27, 2025
@suung suung force-pushed the 60-project-dependent-tool-selection branch from c5c591d to 11d7253 Compare November 2, 2025 20:55
@pessi-v
Copy link
Copy Markdown
Collaborator

pessi-v commented Nov 10, 2025

@suung I can't build and test this. I guess it needs to be rebased first

- Add ProjectDetector using VSCode APIs for language detection
- Enhance ToolsTreeProvider with project-aware tool filtering
- Add VSCode commands: 'Detect Project Languages' and 'Export Project Info for CLI'
- Implement tool compatibility indicators (✓ Compatible / ⚠ Not compatible)
- Add comprehensive e2e tests for project detection system
- Clean API for VSCode to CLI data passing via .carbonara-project-info.json

Resolves #60 - Project dependent tool selection
- Add detectProject and exportProjectInfo commands to integration test expectations
- Update tools-tree-provider test to handle project filtering gracefully
- Fix filterToolsByProject to show all tools when project type is unknown
Defer project detection using setTimeout to ensure it runs after
activation completes. This prevents timing issues in E2E tests where
the extension status bar item might not appear if project detection
runs synchronously during activation.
@suung suung force-pushed the 60-project-dependent-tool-selection branch from eb161a5 to 60d2574 Compare November 11, 2025 14:31
@suung
Copy link
Copy Markdown
Collaborator Author

suung commented Nov 11, 2025

@pessi-v

@suung I can't build and test this. I guess it needs to be rebased first

@pessi-v rebased... I just built a package and it worked, let me know if that's not so

@suung suung requested a review from pessi-v November 11, 2025 14:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Filter tools / Project dependent tool selection

2 participants