Twitter API v2 support #460
Merged
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
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.
Adding support for retrieving user profile information from Twitter API v2 by adding a
twitterv2provider.I had encountered issues retrieving user profile information due to the renaming of properties and changed URL query parameters with the Twitter API v2 as evidenced at https://developer.twitter.com/en/docs/twitter-api/users/lookup/api-reference/get-users-me.
Note
I'm not a developer by trade but have been using Goth for a while and wanted to solve the issues I was encountering with accessing user details with v2 of the Twitter API.
Let me know if there's anything required to improve this PR or whether I may have been going about using the API incorrectly.