orcasgit / django-fitbit Goto Github PK

The 0.1.0 PyPi package does not contain the fixtures directory which causes Django 1.7 migrations to fail. Migration fitapp.0002_initial_data attempts to load data from fixtures/initial_data.json which is not there.

As a temporary workaround, download inital_data.json and place it in a fixtures directory wherever you installed django-fitbit.
https://github.com/orcasgit/django-fitbit/tree/master/fitapp/fixtures

Work on setting up the model or models we'll need in django-fitbit to store the data to be able to access somebody's fitbit. Using the Django User as a key seems reasonable.

It seems the models currently rely use the default value for on_delete in some fields (e.g., the UserFitbit.user field). However, on_delete has become a required argument in Django 2.0.

Does django-fitbit support getting data from non-time-series API endpoints?

e.g. /foods/log only supports getting data for a single date:

GET https://api.fitbit.com/1/user/28H22H/foods/log/date/2015-09-01.json

More info here: https://dev.fitbit.com/docs/food-logging/#get-food-logs

I've hacked something quickly with a get_fitbit_singleday_data function based on get_fitbit_data - if this is the best way I'll make a PR.

Migrating to django 1.11, Will django-fitbit latest version supports django 1.11?

Not sure if I'm doing something wrong, but what happens is that once a user authorizes their account with fitbit, it seems to store some cookies. When I then logout and login as a different user, it still tries to use those cookies. As a result, I am unable to authorize this second user. If I go to incognito for example, without any cookies, I can authorize and fetch data for the second user. What is the right way to support these sort of operations? When the user logs out, I should log out of fitbit as well?

I refered to the documentation but the "getting started" part is too high level. would you kindly make a quick step by step example app and how to use your libraries?

Currently, we redirect the user to the Fitbit integration page if they aren't already integrated. We should let the user know why they've been redirected by providing an in-page error message, or an informational message on the integration page. We can use something like django.contrib.messages to provide the message.

In this function we can lose refresh_token: https://github.com/orcasgit/django-fitbit/blob/master/fitapp/views.py#L120
There is no updates of access_token and refresh_token. I can not understand why you don't want to fix this bug. If you don't like my code: #35 please add yours code to fix this bug.

when we think we're ready

I guess fitbit as lot of devices , like Flex, Charge, Charge HR, One Zip
Can I get data for all of those using this app ?

Use case: user is on the site, clicks something to integrate their fitbit, end up at the fitbit site, click something to authorize us to use their data, we store whatever we need so we can get their data in the future.

It might make sense to break this down into smaller tickets and implement it in parts.