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
Expected result:
3 results between startDate and endDate, in descending order.
Actual result:
10 (all) results between startDate and endDate, in ascending order.
I tried different limits (1, 3, 5, 10), it doesn't effect the result, it seems like the parameters are ignored.
I always get all data between the dates set.
Furthermore, the documentation says:
Datapoints are ordered in an descending fashion (from newer to older)
Although if I skip the 'ascending' parameter, it's still ordered ascending, not descending.
I simply can't change the ordering and by default it's ascending, not descending as described.
The other parameters like startDate or dataType are working perfectly, so the query itself should be fine.
The text was updated successfully, but these errors were encountered:
dariosalvi78
changed the title
Parameters 'limit' and 'ascending' are ignored
Parameters 'limit' and 'ascending' are ignored when querying workouts
Mar 2, 2021
dariosalvi78
changed the title
Parameters 'limit' and 'ascending' are ignored when querying workouts
Parameters 'limit' and 'ascending' are ignored when querying workouts on iOS
Jan 12, 2024
Hi,
It seems like the following parameters are ignored when querying data:
My query looks like this ('start' and 'end' are from type Date):
Expected result:
3 results between startDate and endDate, in descending order.
Actual result:
10 (all) results between startDate and endDate, in ascending order.
I tried different limits (1, 3, 5, 10), it doesn't effect the result, it seems like the parameters are ignored.
I always get all data between the dates set.
Furthermore, the documentation says:
Although if I skip the 'ascending' parameter, it's still ordered ascending, not descending.
I simply can't change the ordering and by default it's ascending, not descending as described.
The other parameters like startDate or dataType are working perfectly, so the query itself should be fine.
The text was updated successfully, but these errors were encountered: