-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOCS][BUG] match-v5 MatchDto: match_id is actually matchId & data_version is actually dataVersion #540
Comments
Same exact thing with the Documentation says |
MingweiSamuel
added a commit
to MingweiSamuel/riotapi-schema
that referenced
this issue
Sep 28, 2021
@ciriousjoker Can you please update the issue title to include both |
MingweiSamuel
added a commit
to MingweiSamuel/Riven
that referenced
this issue
Sep 28, 2021
MingweiSamuel
added a commit
to MingweiSamuel/Riven
that referenced
this issue
Sep 28, 2021
MingweiSamuel
added a commit
to MingweiSamuel/Riven
that referenced
this issue
Sep 28, 2021
ciriousjoker
changed the title
[BUG] match_id is actually called matchId on MatchDto (match-v5)
[BUG] match-v5 MatchDto: match_id is actually matchId & data_version is actually dataVersion
Sep 28, 2021
ciriousjoker
changed the title
[BUG] match-v5 MatchDto: match_id is actually matchId & data_version is actually dataVersion
[DOCS][BUG] match-v5 MatchDto: match_id is actually matchId & data_version is actually dataVersion
Sep 28, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
match_id is actually called matchId on MatchDto (match-v5)
Problem Description
DTO is incorrect.
Expected Result
Actual Result
Developer Impact
Low, you can rename the field in your interface once you realize that things don't work.
Player Impact
None.
Preconditions
User has to read the documentation in the first place instead of generating the interfaces from the json response.
Repro Steps
Make a sample response on the new match-v5 endpoint here:
https://developer.riotgames.com/apis#match-v5/GET_getMatch
Issue Comments
I'm writing this in Javascript, perhaps there's some behind the scenes magic that javascriptifies the field names? I doubt it though since it's also reproducible in the official test environment.
The text was updated successfully, but these errors were encountered: