Skip to content

Fitbit shim should use range queries for step data #33

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.

Sign up for GitHub

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

Jump to bottom
Closed
emersonf opened this issue Dec 10, 2015 · 1 comment
Closed

Fitbit shim should use range queries for step data #33

emersonf opened this issue Dec 10, 2015 · 1 comment
Labels
enhancement

Comments

@emersonf
Copy link
Member

The activities/steps endpoint supports the retrieval of step count data for multiple days, but Shimmer is requesting a day at a time, with repercussions on rate limits and performance.

Shimmer should leverage range queries to optimise the retrieval of step count data.
@emersonf emersonf mentioned this issue Dec 10, 2015
Open
@emersonf
Copy link
Member Author

This has been fixed in release 0.4.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@emersonf