This repository was archived by the owner on Aug 7, 2024. It is now read-only.
migrate api.PostDirectMessage to new twitter api#579
Merged
bear merged 1 commit intobear:masterfrom Sep 29, 2018
Merged
Conversation
|
Any news about this? |
bear
approved these changes
Sep 29, 2018
Owner
bear
left a comment
bear
left a comment
There was a problem hiding this comment.
Reviewed 6 of 6 files at r1.
Reviewable status:complete! all files reviewed, all discussions resolved
bear
approved these changes
Sep 29, 2018
Owner
bear
left a comment
bear
left a comment
There was a problem hiding this comment.
Reviewable status:
This file contains hidden or 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
This PR migrates the existing PostDirectMessage method to use the new Twitter API documented at https://developer.twitter.com/en/docs/direct-messages/sending-and-receiving/api-reference/new-event.
This is a breaking change as both the input format and the response format are quite different; for example
screen_nameis no longer supported as a parameter, and the return result also no longer contains hydratedrecipientandsenderobjects.This change is