✨ (api) getnext track api

[hairmare]

This is a PoC for fixing the API parts needed for #52

• do we want to rerun mutagen or is there a saner way to get the metadata
• ensure coverage doesn't tank by writing some tests
• rebase onto 💚 (api) fix coverage report #54

[codecov-commenter]

Codecov Report

Merging #55 into master will increase coverage by 0.54%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #55      +/-   ##
==========================================
+ Coverage   78.90%   79.44%   +0.54%     
==========================================
  Files           1        1              
  Lines         602      618      +16     
  Branches      141      143       +2     
==========================================
+ Hits          475      491      +16     
  Misses        110      110              
  Partials       17       17              

Impacted Files	Coverage Δ
klangbecken.py	79.44% <100.00%> (+0.54%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b94daa0...6a56eda. Read the comment docs.

[spameier]

I think it would be better to just return the id of next track by the API. The client already has a copy of index.json and can figure out the metadata of the track on his own. What do you think?

[spameier]

The most simple solution would be to fetch /data/prio.m3u directly from the client. Not really sexy though..

[hairmare]

The most simple solution would be to fetch /data/prio.m3u directly from the client. Not really sexy though..

I'll give implementing it directly in the ui a go... Reading from an m3u is just about as unsexy as reading index.json on the client. Not that this code is much more sexy though.

[hairmare]

Extending the API is indeed not needed since the frontend can access prio.m3u directly.

My frontend PR is now updated to not use this change: radiorabe/klangbecken-ui#90