pull response a little weird
Open
Nobody has claimed this yet.
group/api-upgrade
kind/enhancement
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
pull returns a string that's a contamination of one or more JSON strings.
Wouldn't it make more sense to return either that last status as a dict, or a list of status dicts?
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 at the pull entry point and inspect how its response is currently parsed and returned. Clarify whether the API should expose the last status dict or a list of status dicts, then add coverage showing the agreed structured result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100