Description
Each retriever provider accepts a free-form \settings\ dict in the config, but there's no validation that catches typos or invalid setting names. A user might write \collectoin_name\ instead of \collection_name\ and only discover the error at runtime.
What to Do
For each retriever provider, define the expected settings keys and add validation that warns or errors on unknown keys. Start with one or two retrievers:
- \openagent_eval/providers/retrievers/chroma.py\ — settings like \collection_name, \k\
- \openagent_eval/providers/retrievers/qdrant.py\ — settings like \collection_name, \url\
Files to Look At
- \openagent_eval/providers/retrievers/*.py\ — retriever implementations
- \openagent_eval/config/models.py\ — config models
Good First Issue ✅
A practical improvement that prevents a common user frustration.
Description
Each retriever provider accepts a free-form \settings\ dict in the config, but there's no validation that catches typos or invalid setting names. A user might write \collectoin_name\ instead of \collection_name\ and only discover the error at runtime.
What to Do
For each retriever provider, define the expected settings keys and add validation that warns or errors on unknown keys. Start with one or two retrievers:
Files to Look At
Good First Issue ✅
A practical improvement that prevents a common user frustration.