OpenSlides / OpenSlides/openslides-backend
Don't rely on the client to clean up the import_preview
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 40
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 19
Description
In the current implementation, the backend does not delete the import_preview if a participant.import fails.
It expects the client to tell it to delete the import_preview after the client gets an error from participant.import.
We cannot and should not assume that the client calls the cleanup action.
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
Trace the backend flow for participant.import and the import_preview lifecycle, focusing on what happens when the import fails. Determine where server-side cleanup should occur rather than relying on a client cleanup action. Done means a failed participant.import removes its import_preview without requiring a follow-up client request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100