Deserialize responses?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by locating the client’s API response-handling entry point and review how responses are currently exposed. Clarify the intended object shape and scope before implementing, then add coverage showing that responses are deserialized consistently; the issue names no files or tests.
Written by the indexing model from the issue text.
Description
Great work with the client, I was thinking of creating one myself but you've done a great job with this.
Do you have plans to deserialize the responses into objects?
If you're not against it then I am happy to create a PR with the change.
- Dominant language
- Python
- Stars
- 7
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
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.
More from andreagrandi/toshl-python
-
bug
andreagrandi/toshl-python#5 · 1 assignee ·
All issues in andreagrandi/toshl-python
Similar issues
-
agent-ready documentation needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
instance instance add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
searxng/searx-instances#939 · 1 comment ·
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100