API v2 meta-issue
Open
- Dominant language
- Python
- Stars
- 26
- Forks
- 21
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 15
Description
I think it is time to start collecting issues which are to be addressed in a new API version, i.e. that fixing them require a breaking change likely to be done only in v2; or we do not have explicit issue and should be described here
- #1562
- #1228
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the linked issues #1562 and #1228 and the existing discussion on this meta-issue. The issue does not identify files, tests, or a defined API v2 scope, so completion criteria would need to be established before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100