ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
Refactor: Consolidate All Provider Client Init to a Single place
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem?
We have numerous places where provider client initialization occurs, leading to redundancy and potential inconsistencies.
Describe the solution you'd like
- Consolidate all client initialization into a single location.
- Reuse existing BaseProvider methods.
- Ensure compatibility with both sync and async execution.
Original issue
Describe the current behavior
We have many places where provider client initialization happens.
Describe the enhancement you'd like
Consolidate all client init to reuse BaseProvider methods that are already present. This takes care of sync/async execution too.
Why is this enhancement needed?
Explain the benefits (e.g., performance, usability, maintainability, scalability).
Additional context
Add any other context, metrics, screenshots, or examples about the enhancement here.
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 locating BaseProvider and all provider client initialization sites, then map how each is used by synchronous and asynchronous execution. Consolidate those paths around the existing BaseProvider methods, preserving both execution modes; done means initialization has one location and all providers continue to work consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100