Right now sources have include/exclude glob patterns for paths, but there's no straightforward way to say "only index .yml and .md files" without writing glob syntax.
The idea: add a multi-select dropdown above the existing glob fields. Populated with all the formats OneSearch supports (.pdf, .md, .txt, .docx, .xlsx, .pptx, .yml, .json, etc). Users pick the ones they want, they show as chips/tags. If nothing is selected, it indexes all supported types.
Backend gets a new file_types field on the source model — separate from glob patterns. Glob fields stay for power users who want path-based filtering like **/node_modules/**.
Casual users get a clean picker, advanced users still have globs. Both work together.
Right now sources have include/exclude glob patterns for paths, but there's no straightforward way to say "only index .yml and .md files" without writing glob syntax.
The idea: add a multi-select dropdown above the existing glob fields. Populated with all the formats OneSearch supports (.pdf, .md, .txt, .docx, .xlsx, .pptx, .yml, .json, etc). Users pick the ones they want, they show as chips/tags. If nothing is selected, it indexes all supported types.
Backend gets a new
file_typesfield on the source model — separate from glob patterns. Glob fields stay for power users who want path-based filtering like**/node_modules/**.Casual users get a clean picker, advanced users still have globs. Both work together.