luanti-org / luanti-org/contentdb
Collections containing deleted content breaks when retrieving via API
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 115
- Forks
- 62
- Avg merge
- 19h 7m
- Merged PRs (30d)
- 5
Description
Summary
When you have an existing collection containing a mod that's been deleted, that collection cannot be accessed via the API, instead it serves a 500 Server Error response.
Steps to reproduce
I've kept a broken collection here for reference: https://content.luanti.org/collections/shrimp/broken/
It loads via the UI, however accessing this via the API at https://content.luanti.org/api/collections/shrimp/broken/ returns a 500 Server Error.
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
Reproduce the failure with the broken collection at /api/collections/shrimp/broken/ and compare it with the UI URL, which still loads. Trace the API entry point and the collection serialization path to identify how deleted mods are handled. Done means this collection is returned through the API without a 500 response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100