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
Currently there is a new enforced pagination on the matchlist endpoint that might cause requests to fail bc they
a) have a too high range (>=100) for their beginIndex/endIndex done in Colorfulstan/LeagueJS@d97c533
b) have a too high range (> 1week) for their startTime/endTime
If a higher range is given, the Endpoint methods should ideally split the ranges and execute the neccessary requests in the background I think
The text was updated successfully, but these errors were encountered:
check and split beginIndex - endIndex (batches of 100)
check and split beginTime - endTime (1 week intervals)
if only beginIndex given: set endIndex +100
if only endIndex given: set beginIndex -100
if only beginTime given: set endTime +1week
if only endTime given: set beginTime -1week
There might be value in a method that returns an observable, but since the batches need to be requested in series anyway (du to missing filtered totalGames indication on the API) for now it will just return a Promise that resolves in a combined array of MatchReferences
Watch how
https://discussion.developer.riotgames.com/questions/3155/why-pagination-is-a-problem.html
evolves.
Currently there is a new enforced pagination on the matchlist endpoint that might cause requests to fail bc they
a)
have a too high range (>=100) for their beginIndex/endIndexdone in Colorfulstan/LeagueJS@d97c533b) have a too high range (> 1week) for their startTime/endTime
If a higher range is given, the Endpoint methods should ideally split the ranges and execute the neccessary requests in the background I think
The text was updated successfully, but these errors were encountered: