Asynchronous Copy/Move
Open
Nobody has claimed this yet.
04 type: enhancement
- Dominant language
- Python
- Stars
- 109
- Forks
- 107
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 4
Description
We have a synchronous copy/move endpoint already. Though, for large content trees, an asynchronous endpoint or behavior would be helpful. We decided to not tackle this in the first step because the implementation might be complex (at least if we do not want to make any assumptions about the underlying implementation).
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 the existing synchronous copy/move endpoint and reviewing how it handles large content trees. Define the asynchronous endpoint or behavior and its completion semantics without assuming a particular underlying implementation; the work is done when large copy/move operations can run asynchronously through the REST API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100