You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Members/admin should be able to like or dislike a track in the queue via REST API. Liking/disliking the currently playing track is possible via the POST /api/v1/jukebox/{jukebox_id}/player-state route, use that as inspiration. A new route will probably need to be created, along with a new set of DTOs.
After dis/liking a track in the queue, make sure to emit the track-queue-update in the websocket to update all of the frontends (via JukeboxGateway.emitTrackQueueUpdate).
When referring to the queue, ignore the default spotify queue that shows up if "our" queue is empty. We only need to store data on tracks in the queue that "we" manage.
Tasks
Should be able to like any track in queue
Should be able to dislike any track in queue
Websocket is called when liking a track
Websocket is called when disliking a track
The text was updated successfully, but these errors were encountered:
Info
Members/admin should be able to like or dislike a track in the queue via REST API. Liking/disliking the currently playing track is possible via the
POST /api/v1/jukebox/{jukebox_id}/player-state
route, use that as inspiration. A new route will probably need to be created, along with a new set of DTOs.After dis/liking a track in the queue, make sure to emit the
track-queue-update
in the websocket to update all of the frontends (viaJukeboxGateway.emitTrackQueueUpdate
).When referring to the queue, ignore the default spotify queue that shows up if "our" queue is empty. We only need to store data on tracks in the queue that "we" manage.
Tasks
The text was updated successfully, but these errors were encountered: