forked from dghubble/go-twitter
-
Notifications
You must be signed in to change notification settings - Fork 2
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
WIP: Updating fork #6
Open
thomas-tharp
wants to merge
38
commits into
master
Choose a base branch
from
updating-fork
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
* Drop Go 1.6 and 1.7 coverage
* Fix DirectMessageEvent id and sender/recipient id to be strings. Comparing API docs with prior docs shows the intended shift toward strings * Deprecate DirectMessage service's Show, Get, New, Sent, and Destroy methods. * Add small example of usage
* Apps string field doesn't match actual JSON responses
* golint previously supported both a golang.org and github.com import path. Recently, they switched to allowing only the golang.org path * golang/lint@9a27203
* Test stream server HandleFunc's stream an expected message and then return an HTTP error response code to break stream retrying, so received messages can be checked * Tests erroneously used 130 as the HTTP error response code (130 is the Twitter code). Starting in Go v1.11, such invalid HTTP response codes cause the connection to the test stream server to hang, causing tests to hang. * Fix the error code to be 500, some valid HTTP status code that isn't handled specially (e.g. no backoff)
* Add `EventsNew` method for sending a Direct Message event * Add `EventsShow` method for getting a single Direct Message event * Add missing test coverage for `EventsList` method * Add`EventsDestroy` method for destroying a Direct Message event * Move DirectMessageEvents example to its own `go run`-able file * https://developer.twitter.com/en/docs/direct-messages/api-features
* Roll out standard Makefile across projects
* user_id is a comma separated list of user IDs
* Add `Since` and `Filter` to SearchTweetParams
* Ensure examples and their dependencies aren't included in the twitter package dependencies
* Use the "two-legged OAuth 2.0" oauth2/clientcredentials
helper to obtain app auth tokens automatically
* Close #88
* Previous links redirected to a mostly useless introduction page
* Add support for stream errors to message channel
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.
No description provided.