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
Bug Description
Error in Match V5's ParticipantDto and ChallengeDto Documentation.
Problem Description
ChallengeDto:
Fields earliestBaron, earliestDragonTakedown, earliestElderDragon, fastestLegendary and thirdInhibitorDestroyedTime are incorrectly documented as Integers while they can be Floats.
ParticipantDto:
Fields playerAugment5 and playerAugment6 are missing from the documentation while being present on request.
Expected
Documentation should be consistent with reality.
Developer Impact
Might cause misusage of the API if the developers don't double checks before usage.
Repro Steps for the false integer value
Do a get match request for the match "EUW1_7071521501" (for instance).
Check the value for earliestDragonTakedown in multiples ChallengeDto, which is Floating Point Number.
The text was updated successfully, but these errors were encountered:
noahkohrs
changed the title
[BUG] Incorrect documentation for Match API.
Incorrect documentation for Match API.
Aug 17, 2024
Bug Description
Error in Match V5's ParticipantDto and ChallengeDto Documentation.
Problem Description
ChallengeDto:
Fields earliestBaron, earliestDragonTakedown, earliestElderDragon, fastestLegendary and thirdInhibitorDestroyedTime are incorrectly documented as Integers while they can be Floats.
ParticipantDto:
Fields playerAugment5 and playerAugment6 are missing from the documentation while being present on request.
Expected
Documentation should be consistent with reality.
Developer Impact
Might cause misusage of the API if the developers don't double checks before usage.
Repro Steps for the false integer value
The text was updated successfully, but these errors were encountered: