feat(indexing): support custom file extensions - #12306
Conversation
05b54a5 to
c081f58
Compare
Code Review SummaryStatus: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (incremental: 1 file)
Only change since the previous review is a line-wrap formatting fix to the Korean translation string for Fix these issues in Kilo Cloud Previous Review Summaries (2 snapshots, latest commit ca19c85)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit ca19c85)Status: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (incremental: 19 i18n files)
Only additive translation strings for the new Fix these issues in Kilo Cloud Previous review (commit c081f58)Status: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (32 files)
Reviewed by claude-sonnet-5 · Input: 34 · Output: 5.4K · Cached: 745.3K Review guidance: REVIEW.md from base branch |
…s-for-indexing feat(indexing): support custom file extensions
Codebase indexing currently uses a fixed built-in extension list, which prevents projects from limiting indexing work to relevant formats or admitting additional text formats.
Add an optional
indexing.fileExtensionsallowlist. When configured, it replaces the built-in extension set across full scans, file watching, parsing, stale-result filtering, and worktree searches. Values are normalized case-insensitively, custom text formats use fallback chunking, and omitted configuration preserves the existing defaults.Expose the setting in the CLI, VS Code, and Console configuration surfaces, and document its replacement semantics.
Closes #12299.