mirror of
https://github.com/Rigellute/spotify-tui.git
synced 2026-04-26 16:15:55 +03:00
[GH-ISSUE #929] API to expose data that is not available through the CLI #402
Labels
No labels
bug
enhancement
good first issue
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-tui#402
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @KadoBOT on GitHub (Dec 28, 2021).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/929
Hello!
First of all, thanks for the effort you guys put into this. It's impressive!
Recently, I've built a nvim plugin to control Spotify TUI from the editor. And now I was wondering: how hard it is to expose the whole data that is returned from the API calls through another API so tools like the one I've built can extend Spotify TUI? e.g.: I want to know the release date of the album of a track
GetTrack API -> album -> release_date.At least for my use case, a simple command, where I can enter the URL, use the client from Spotify TUI, and fetch the JSON response would be enough. But maybe this can be more elaborated in the future.
If you guys are interested in this idea, I can help with this feature. Let me know.
Thanks!
@fivestones commented on GitHub (Jun 26, 2022):
I'm wondering the same. I'd like to see recently played songs and podcasts from a command on the command line.