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
When sorted with sortKey=createdAt&desc=false, it returns orders starting with "createdAt": 1677266409.
When sorted with sortKey=createdAt&desc=true, it returns orders starting with "createdAt": 1677247163306.
Notice the first query returns createdAt with 10 digits, but the second query returns createdAt with 13 digits. This means the orders API contain createdAt values with both second and millisecond units, making the sort unusable. Orders in milliseconds from 9 months ago are interpreted as newer than orders today in seconds.
Referring to the UniswapX swagger docs to query orders...
sortKey=createdAt&desc=false
, it returns orders starting with"createdAt": 1677266409
.sortKey=createdAt&desc=true
, it returns orders starting with"createdAt": 1677247163306
.Notice the first query returns
createdAt
with 10 digits, but the second query returnscreatedAt
with 13 digits. This means the orders API containcreatedAt
values with both second and millisecond units, making the sort unusable. Orders in milliseconds from 9 months ago are interpreted as newer than orders today in seconds.Reproducible steps
The text was updated successfully, but these errors were encountered: