interledger / interledger/open-payments-python-sdk
Abstract http requests API definitions to avoid repetitive implementations
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Even though we dont have many functions to implement the client HTTP requests we could benefit of some abstraction to not re-implement the same stuff all the time eg:
- build-url
- validate input using pydantic
- dump to json friendly python objects
- send requests
- validate responses using pydantic
- serialize json to python objects
We could reduce footprint with some sort of router.
Contributor guide
No contributing guide indexed for this repository
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 surveying the existing client HTTP request implementations and their Pydantic validation and serialization steps. Compare the repeated URL-building, request, response-validation, and object-conversion flows before proposing a shared router abstraction. Done means the repeated implementations are consolidated without changing the client API behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100