Feature: support for user defined interceptors
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 415
- Forks
- 83
- Avg merge
- 2h 20m
- Merged PRs (30d)
- 3
Description
Currently, Qdrant client only supports authentication via API key through the built-in TokenInterceptor. However, there are many scenarios where users need to add custom headers to requests like 'authorization' header for JWT
I've implemented a solution that makes the client generic over the interceptor type, allowing users to provide their own interceptors that can modify requests arbitrarily: https://github.com/qdrant/rust-client/pull/266
@timvisee
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed implementation in PR #266, which is linked from the issue. Check how the client becomes generic over the interceptor type and how custom request headers are supported; done means user-defined interceptors can modify requests while the existing TokenInterceptor behavior remains supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100