mirror of
https://github.com/Rigellute/spotify-tui.git
synced 2026-04-26 16:15:55 +03:00
[PR #128] [MERGED] Add support for scrolling up/down when album list is active #620
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#620
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?
📋 Pull Request Information
Original PR: https://github.com/Rigellute/spotify-tui/pull/128
Author: @ghost
Created: 11/3/2019
Status: ✅ Merged
Merged: 11/3/2019
Merged by: @Rigellute
Base:
master← Head:scroll-album-list📝 Commits (2)
d6831d3Add support for scrolling up/down when album list is active14b093duse!is_emptyinstead oflen() > 0📊 Changes
3 files changed (+43 additions, -11 deletions)
View changed files
📝
src/app.rs(+39 -0)📝
src/handlers/album_list.rs(+2 -0)📝
src/handlers/library.rs(+2 -11)📄 Description
This PR is related to #11
ctrl+d/ushould scroll through pages but this has been implemented in "Liked Songs" view only. In this PR, I tried to implement scrolling down/up in the "Albums" view.need to confirm:
In
src/app.rs, I added three methods (get_current_user_saved_albums,get_current_user_saved_albums_next, andget_current_user_saved_albums_previous) forApp. These methods are imitation of**saved_tracks**methods. Althoughpush_navigation_stackis called inget_current_user_saved_tracks, I did NOT callpush_navigation_stackinget_current_user_saved_albums. Ifpush_navigation_stackis called after each page scrolling, same contents are pushed into the stack. Scrolling pages several time, q key (go back) seems foul-up. This behavior seems a bug for me so I did not callpush_navigation_stackinget_current_user_saved_albums.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.