[Twitter service] support for 280 characters on non streaming api calls #2103
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
azchohfi
approved these changes
May 16, 2018
hermitdave
approved these changes
May 17, 2018
|
@nmetulev Should we not use |
|
@Odonno, what example? |
|
The JSON object at the end of this page https://developer.twitter.com/en/docs/tweets/tweet-updates |
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.
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Non streaming api calls do not include the full 280 characters of tweets
What is the new behavior?
All api calls now include the full 280 characters
Reference twitter docs: https://developer.twitter.com/en/docs/tweets/tweet-updates
PR Checklist
Please check if your PR fulfills the following requirements: