Should .vscode/launch.json be committed to the repo?

[mircealungu]

Raised while reviewing PR #81 — the PR modifies .vscode/launch.json adding C# debug configs and Python CLI launch configs.

Current state: The file contains developer-specific settings including hardcoded paths to local test projects (test_projects/calibre, test_projects/zeeguu, etc.) that won't exist for all contributors.

Question: Should we keep .vscode/launch.json in the repo or .gitignore it?

Arguments for removing / gitignoring:

• Contains local paths that vary per developer
• IDE config is typically personal preference
• Can cause noisy diffs when different contributors modify it

Arguments for keeping:

• Provides useful debug configurations for new contributors (Python CLI, C# debug)
• Lowers the barrier to entry for development
• The launch configs document how to run/debug the project

One possible middle ground: keep a .vscode/launch.json.example that contributors can copy locally.

🤖 Generated with Claude Code