You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SpotifyClient.UserProfile.GetTopArtists and SpotifyClient.UserProfile.GetTopTracks methods return UsersTopArtistsResponse and UsersTopTracksResponse objects respectively, which seem identical to Paginate<FullArtist> and Paginate<FullTrack> with the exception that they don't implement IPaginatable, so they can't be used in SpotifyClient.Paginate. Was that a conscious design choice to avoid pagination? Because that feels counter-intuitive to me, since the top artists and tracks seem like prime examples of data that should be paginated, as there can be lots of them
The text was updated successfully, but these errors were encountered:
The
SpotifyClient.UserProfile.GetTopArtists
andSpotifyClient.UserProfile.GetTopTracks
methods returnUsersTopArtistsResponse
andUsersTopTracksResponse
objects respectively, which seem identical toPaginate<FullArtist>
andPaginate<FullTrack>
with the exception that they don't implementIPaginatable
, so they can't be used inSpotifyClient.Paginate
. Was that a conscious design choice to avoid pagination? Because that feels counter-intuitive to me, since the top artists and tracks seem like prime examples of data that should be paginated, as there can be lots of themThe text was updated successfully, but these errors were encountered: