UniversalMediaServer / UniversalMediaServer/api
Store multiple osdbhashes per media
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 12
- Forks
- 3
- Avg merge
- 16d 31m
- Merged PRs (30d)
- 6
Description
At the moment that field in the collection is just a string, which is incorrect because many osdbhashes relate to each IMDb ID, which may cause some unexpected behaviours in the code
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
Start by locating the collection schema or model that defines the osdbhash field, then inspect the code that reads and writes it. Done means the collection can represent multiple osdbhashes for one IMDb ID without the unexpected behaviours described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, typescript
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100