This needs to be fleshed out more. What do we want the behavior be when a Jukebox playlist already exists? Can't clutter user's playlist space but want persistence... For now, let's call them all jukebox and on the UI mention that if you like it you should change the name before generating another jukebox
expose createPlaylist(accessToken, name) that wraps Spotify API's createPlaylist()
This needs to be fleshed out more. What do we want the behavior be when a Jukebox playlist already exists? Can't clutter user's playlist space but want persistence... For now, let's call them all jukebox and on the UI mention that if you like it you should change the name before generating another jukebox
expose createPlaylist(accessToken, name) that wraps Spotify API's createPlaylist()