[WIP] Update and fix backend code for Spotify-TUI#3
Open
Copilot wants to merge 4 commits into
Open
Conversation
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Updated rspotify from 0.10 to 0.13 (major API changes) - Updated tokio from 0.2 to 1.x (async runtime update) - Replaced tui with ratatui 0.26.0 (fork/successor) - Updated clap from 2.33 to 4.5 (CLI framework) - Added chrono and clap_complete dependencies - Refactored authentication flow for new rspotify API - Updated network.rs with new Spotify API integration - Fixed type renames: PlayingItem→PlayableItem, PlaylistTrack→PlaylistItem - Fixed Duration handling (duration_ms→duration.num_milliseconds()) - Updated Frame type for ratatui (removed generic parameter) - Fixed Spans→Line rename for ratatui Co-authored-by: AntoneBrewer <16599519+AntoneBrewer@users.noreply.github.com>
- Update CLI modules for clap v4 API changes - Fix ArgMatches API changes (get_flag, get_one, get_count) - Fix rspotify ID types (.id() method via trait import) - Update duration fields (duration_ms → duration.num_milliseconds()) - Fix progress field (progress_ms → progress) - Update playlist_items → playlist_items_manual for pagination - Update get_saved_show_manual parameters - Update redirect_uri.rs for new auth flow Co-authored-by: AntoneBrewer <16599519+AntoneBrewer@users.noreply.github.com>
Co-authored-by: AntoneBrewer <16599519+AntoneBrewer@users.noreply.github.com>
Copilot stopped work on behalf of
AntoneBrewer due to an error
November 26, 2025 11:17
|
Hey @AntoneBrewer , so excited to see someone with an active fork of spotify-tui! I was planning to do the same as you, fork and re-factor. Any other plans that what is in this Copilot plan? Also, are you planning to build/publish packages anytime soon with this repo? Thanks and looking forward to seeing what you do next with this repo! (after copilot tokens get refreshed of course! 😆 ) |
Owner
|
Hi Knox,
Thank you for reaching out and for your interest in the spotify-tui fork.
The current plan for PR #3, which is focused on fixing and updating the
backend, includes:
1. Resolving application startup issues (e.g., 'localhost' bindings and
port problems).
2. Updating Spotify API integration (scopes, token handling, and playback
controls).
3. Refactoring deprecated dependencies.
4. General code cleanup and optimization.
5. Comprehensive testing.
I am certainly open to extending the plans beyond this initial scope. Were
there any specific features or refactoring you had in mind that are not
covered by the current plan?
Regarding your question about publishing packages, that is a long-term
goal, but my immediate priority is stabilizing the code base.
If you are interested in contributing, I would greatly appreciate any help
with the repository. Please let me know if you have a particular area you
would like to work on, or if you have suggestions for what should be
prioritized next.
Best,
Antone
…On Sun, Nov 30, 2025 at 3:24 PM Knox Lively ***@***.***> wrote:
*gonzolively* left a comment (AntoneBrewer/spotify-tui#3)
<#3 (comment)>
Hey @AntoneBrewer <https://github.com/AntoneBrewer> , so excited to see
someone with an active fork of spotify-tui! I was planning to do the same
as you, fork and re-factor. Any other plans that what is in this Copilot
plan?
Also, are you planning to build/publish packages anytime soon with this
repo?
Thanks and looking forward to seeing what you do next with this repo!
(after copilot tokens get refreshed of course! 😆 )
—
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD6UTX3GGPD74QGHSO3IZ4L37NG7LAVCNFSM6AAAAACNH2PTK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKOJTGI4TKMBSGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Original prompt
This pull request was created as a result of the following prompt from Copilot chat.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.