Error OnGetRecentTradesAsync() parsing json from token

[ferib]

Json parsing error on ExchangeKuCoinAPI.cs#219
After fixing the KC- headers its now giving a correct result in "token".
But the "token" result is not handler correctly.

[GonzoKK]

I took a stab at this. Both OnGetRecentTradesAsync and OnGetHistoricalTradesAsync seem to be working now.

Download link for ExchangeKuCoinAPI.cs
http://k00.fr/pi9jssl8

protected override async Task<IEnumerable<ExchangeTrade>> OnGetRecentTradesAsync(string marketSymbol, int? limit = null)
{
	//limit is always 100
    List<ExchangeTrade> trades = new List<ExchangeTrade>();
	string url = "/market/histories?symbol=" + marketSymbol ; 
	JToken obj = await MakeJsonRequestAsync<JToken>(url);
	if(obj.HasValues) { //
		foreach(JToken trade in obj) {    
			trades.Add(trade.ParseTrade("size", "price", "side", "time", TimestampType.UnixNanoseconds, idKey: "sequence"));
			//trades.Add(trade.ParseTrade("size", "price", "side", "time", TimestampType.UnixMilliseconds, idKey: "tradeId"));
		}
	}
    return trades.AsEnumerable().Reverse(); //descending - ie from newest to oldest trades
}

protected override async Task OnGetHistoricalTradesAsync(Func<IEnumerable<ExchangeTrade>, bool> callback, string marketSymbol, DateTime? startDate = null, DateTime? endDate = null, int? limit = null)
{
    List<ExchangeTrade> trades = new List<ExchangeTrade>();
    JToken token = await MakeJsonRequestAsync<JToken>("/market/histories?symbol=" + marketSymbol + (startDate == null ? string.Empty : "&since=" + startDate.Value.UnixTimestampFromDateTimeMilliseconds()));
    foreach (JObject trade in token)
    {
        trades.Add(trade.ParseTrade("size", "price", "side", "time", TimestampType.UnixNanoseconds, idKey: "sequence"));
		//trades.Add(trade.ParseTrade("size", "price", "side", "time", TimestampType.UnixMilliseconds, idKey: "tradeId"));
    }
    var rc = callback?.Invoke(trades);
}

[GonzoKK]

FYI - UnixMilliseconds throws an .ArgumentOutOfRangeException

[ferib]

@GonzoKK awesome fix there, open a PR and hopefully your fix will be added in the next NuGet version