Skip to content
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.

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

is it better not to extract resp from proivder in callback()? #138

Open
chungwong opened this issue Nov 14, 2013 · 0 comments
Open

is it better not to extract resp from proivder in callback()? #138

chungwong opened this issue Nov 14, 2013 · 0 comments

Comments

@chungwong
Copy link

currently all callback functions for all providers are extracting different info from the response returned by providers.

For example, facebook.py extracts timezone,gender and birthday and append them into profile while tiwtter extract some different, extra data like addresses.

I am not sure how to override the callback function on the fly to extract additional data from the response to the profile variable as they are hard coded before the view get the profile.

Is it better just return the raw response to the view by context?
That way the view can do whatever it wants to the response rather than a harde coded profile with limited and inconsistent data?

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant