Web API: data versions
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 2.1k
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 31
Description
Hi there,
High priority:
- I'm currently working on improving the beets integration in Tomahawk Media Player (both desktop and android versions). A feature I'd really love to see would be to have a simple revision string returned in the /stats response from the web plugin. A simple timestamp indicating the last modification would be enough. That way I would be able to only re-fetch the beets collection data when necessary and not on every start-up.
Low priority:
- Even more awesome would be if I'd be able to give that timestamp to a query like /item/diff/$timestamp and get a list of all added/modified and removed items since that given timestamp. That would obviously be more efficient and should improve performance even further :)
- Another thing that'd be real handy would be to have some way of getting the beets version through the web plugin. I'd like to make sure that every necessary feature is supported by beets before initializing the collection in Tomahawk.
Thanks!
Contributor guide
Research direction
Start by locating the web plugin entry points for /stats, /item/diff/$timestamp, and version reporting. Clarify the timestamp semantics and response formats before implementing; done should include incremental added, modified, and removed items plus a way to identify the beets version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100