From bbc6968176a78deafecd0ccb9d5f044a73c0e24a Mon Sep 17 00:00:00 2001 From: Rikki Tooley Date: Tue, 1 Sep 2015 02:36:17 +0100 Subject: [PATCH] Change default page value for user.getRecentTracks from 0 to 1 API seems to have changed behaviour - page=1 no longer contains "now playing" track as its first item - page=0 no longer returns same as page=1 but without the "now playing" track See #78 --- src/IF.Lastfm.Core/Api/UserApi.cs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/IF.Lastfm.Core/Api/UserApi.cs b/src/IF.Lastfm.Core/Api/UserApi.cs index 6c0b4422..6d730eda 100644 --- a/src/IF.Lastfm.Core/Api/UserApi.cs +++ b/src/IF.Lastfm.Core/Api/UserApi.cs @@ -50,7 +50,7 @@ public async Task> GetTopAlbums(string username, LastSta /// Page numbering starts from 1. If set to 0, will not include the "now playing" track /// Amount of scrobbles to return for this page. /// Enumerable of LastTrack - public async Task> GetRecentScrobbles(string username, DateTimeOffset? since = null, int pagenumber = 0, int count = LastFm.DefaultPageLength) + public async Task> GetRecentScrobbles(string username, DateTimeOffset? since = null, int pagenumber = 1, int count = LastFm.DefaultPageLength) { var command = new GetRecentTracksCommand(Auth, username) {