Closed tsani closed 7 years ago
Alternatively we can just say "too bad" because this can already be implemented client-side. (And has been implemented in the labdl script.)
As mentioned in the previous comment, we're not going to complicate the webservice API and instead just require clients to do this themselves.
See #1. With the refactor of
/tracks
proposed therein, we could implement a query-string parameterenqueue_at
specifying that the acquired tracks should be enqueued at the given position. The position specifier would be the same as theposition
query-string parameter forPUT /playlist
. Because we can't distinguish between a parameter being present but failing to parse and a parameter being absent, we will assume that that ifenqueue_at
isNothing
, then no enqueuing is to be performed. We can implement an additional query-string flagenqueue
(no_at
) whose value is ignored, but that serves to indicate that the default behaviour forPUT /playlist
of enqueuing after the currently playing track in the playlist is desired.