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
LoL's match-v5 allows for queue and type query parameters to be passed to the matches/by-puuid/{puuid}/ids method. This causes it to return a list of match IDs filtered by either of them. The exact same method in tft-match-v1 lacks these two parameters,
I have a use-case where I only care about the latest ranked game for a given player. This is trivial to do with the LoL API as I can set the queue ID to that of Ranked Solo/Duo and the number of returned matches to 1. I believe this is not a necessarily unusual use case for smaller projects using the API, although I will admit larger projects like match history sites are unlikely to encounter this.
The best way I can see to achieve this with tft-match-v1 is to request a bunch of match IDs, then iterate through them and make a request to matches/{matchId} to check the queue ID. This itself would potentially need to be iterative until you reach some arbitrary limit of matches to look through before stopping. The DX of this is obviously worse and significantly increases the amount of API calls that need to be made for any adjacent use-cases. Additionally, two-way traffic needlessly increases as a matches/{matchId} call contains a large amount of data which has a good chance of being ignored.
Implementing these query parameters seems like a logical upgrade to tft-match-v1 to bring it more inline with match-v5.
The text was updated successfully, but these errors were encountered:
tomwmth
changed the title
Allow filtering TFT matches by queue ID and/or type
[FEATURE-REQUEST] Allow filtering TFT matches by queue ID and/or type
May 23, 2024
LoL's
match-v5
allows forqueue
andtype
query parameters to be passed to thematches/by-puuid/{puuid}/ids
method. This causes it to return a list of match IDs filtered by either of them. The exact same method intft-match-v1
lacks these two parameters,I have a use-case where I only care about the latest ranked game for a given player. This is trivial to do with the LoL API as I can set the queue ID to that of Ranked Solo/Duo and the number of returned matches to 1. I believe this is not a necessarily unusual use case for smaller projects using the API, although I will admit larger projects like match history sites are unlikely to encounter this.
The best way I can see to achieve this with
tft-match-v1
is to request a bunch of match IDs, then iterate through them and make a request tomatches/{matchId}
to check the queue ID. This itself would potentially need to be iterative until you reach some arbitrary limit of matches to look through before stopping. The DX of this is obviously worse and significantly increases the amount of API calls that need to be made for any adjacent use-cases. Additionally, two-way traffic needlessly increases as amatches/{matchId}
call contains a large amount of data which has a good chance of being ignored.Implementing these query parameters seems like a logical upgrade to
tft-match-v1
to bring it more inline withmatch-v5
.The text was updated successfully, but these errors were encountered: