Did you encounter this recently, or has this bug always been there? Yes recently (today)
Expected behaviour:
For request player/:tag/battles with only 1 tag shall be a list of 25 battles (not lists in a list) as described in closed issue #401 => it is OK since fix of issue #401
But for request with multiple tags player/:tag1,:tag2/battles, the result shall be a list (for each tag) of lists of 25 battles (previous behaviour of the api).
But since fix of issue #401, the result is only a big list of battles of all players (if 2 tags, result is a list of 50 battles).
Request Details:
GET
https://api.royaleapi.com/player/920UP9,QPQPUGGU/battles
I adapted my code accordingly to these new response but maybe it would be useful to get back to previous behavior or to keep this new response but to inform developpers of this API modification.
Issue Report:
For request player/:tag/battles with only 1 tag shall be a list of 25 battles (not lists in a list) as described in closed issue #401 => it is OK since fix of issue #401
But for request with multiple tags player/:tag1,:tag2/battles, the result shall be a list (for each tag) of lists of 25 battles (previous behaviour of the api). But since fix of issue #401, the result is only a big list of battles of all players (if 2 tags, result is a list of 50 battles).
Request Details:
Response Details:
Result is:
Instead of:
I adapted my code accordingly to these new response but maybe it would be useful to get back to previous behavior or to keep this new response but to inform developpers of this API modification.