Torjus Håkestad
730f2d7610
When indexing a revision that already exists, the indexer now returns early with information about the existing revision instead of re-indexing. Use the --force flag to re-index an existing revision. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
19 lines
764 B
Markdown
19 lines
764 B
Markdown
# TODO - Future Improvements
|
|
|
|
## Usability
|
|
|
|
- [ ] Progress reporting during indexing ("Fetching nixpkgs... Parsing options... Indexing files...")
|
|
- [ ] Add `search_files` MCP tool - search for files by path pattern (e.g., find all nginx-related modules)
|
|
|
|
## Robustness
|
|
|
|
- [ ] PostgreSQL integration tests with testcontainers (currently skipped without manual DB setup)
|
|
- [ ] Graceful handling of concurrent indexing (what happens if two clients index the same revision?)
|
|
|
|
## Nice to Have
|
|
|
|
- [ ] Option history/diff - compare options between two revisions ("what changed in services.nginx between 24.05 and 24.11?")
|
|
- [ ] Auto-cleanup - prune old revisions after N days or keep only N most recent
|
|
- [ ] Man page generation
|
|
- [ ] Shell completions (bash, zsh, fish)
|