Skip to content

Conversation

@Bentroen
Copy link
Member

This pull request implements all changes delimited in #67, effectively concluding the implementation of #44.

As of this pull request, the song pagination already uses the exact same component as the 'Recent songs' view (LoadMoreButton), so merging this also closes #70.

It's not the focus, the content is - we can make it as simple and unobtrusive as possible.
Removed loading overlay appearing during a filter or query change.

Removed separate skeleton loading component tree in favor of making each leaf component aware of its state and capable of displaying itself as a skeleton (WIP), as recommended by `react-loading-skeleton`.

See:
https://github.com/dvtng/react-loading-skeleton#dont-make-dedicated-skeleton-screens
Makes it consistent with 'My songs'.
(shh... don't tell anyone... but... the three dots icon already serves this purpose!!)
We've had Next.js complain about importing tons of stuff from the `@nbw/database` module into the client bundle, even though we already imported `SongPreviewDtoType` from that package before. I've decided to inline the enums and add a TODO so we can look deeper into that issue later. That's still better than going back to the magic strings :)
Replaces and combines the functionality of methods `getSongsByCategory`, `getRecentSongs` and `searchSongs` into a generic `querySongs` method that supports all parameters.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Implement pagination with the same button as the 'Recent songs' section

2 participants