Remove V1.1 verify_credentials call after successful token retrieval #26
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
na2hiro
force-pushed
the
remove-deprecated-api-calls
branch
from
fc5d161
to
e2469f9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Today, auth process goes like this
/oauth/request_token(OAuth 1.0a): Retrieve request token/oauth/access_token(OAuth 1.0a): Retrieve access tokens (as well as user id and screen name)/1.1/account/verify_credentials.json(Twitter API 1.1): Get user's full profile using the access tokensI think the last step causes issue in near future due to the API deprecation / migration to the new subscription model. This is to remove the last call and return a simple profile which consists of only user id and screen name.