/time sometimes returns invalid time IDs #15
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Example query: https://api.strafes.net/api/v1/time?page_size=100&page_number=1&game_id=1&mode_id=0&style_id=1&user_id=1545614420&sort_by=3
In the response I see
These IDs do not work when used with endpoints that require time ID (like the newly released /time/placement/) and they look too large, so I'm guessing that they are wrong.
So large IDs are valid but the ones being returned seem to to be incorrect. Probably a bad integer conversion somewhere.
825832845792641000should be825832845792641027So looking into it further, if you just run the raw query with curl:
You get the correct response:
Which means this is a Javascript skill issue and everything is working fine from what the API itself is responding with.
I'll graciously convert it to a string so your browser language can handle it. #16
Let me know if you can't handle anything else. 😊
javascript moment...
/time/placement still returns the ID as a number, mind updating that? I can workaround it by forcing the ID to get parsed as a string but if you updated /times and /times/worldrecord already might as well make it consistent all around.
Done
208f5c0b75