Wrapper for the Twitter REST API
@note All methods have been separated into modules and follow the same grouping used in {dev.twitter.com/doc the Twitter API Documentation}. @see dev.twitter.com/pages/every_developer
@return [Boolean]
# File lib/twitter/rest/client.rb, line 112 def bearer_token? !!bearer_token end
# File lib/twitter/rest/client.rb, line 55 def connection_options @connection_options ||= { :builder => middleware, :headers => { :accept => 'application/json', :user_agent => user_agent, }, :request => { :open_timeout => 5, :timeout => 10, }, } end
@return [Boolean]
# File lib/twitter/rest/client.rb, line 117 def credentials? super || bearer_token? end
Perform an HTTP DELETE request
# File lib/twitter/rest/client.rb, line 91 def delete(path, params = {}) request(:delete, path, params) end
Perform an HTTP GET request
# File lib/twitter/rest/client.rb, line 96 def get(path, params = {}) request(:get, path, params) end
@note Faraday's middleware stack implementation is comparable to that of Rack middleware. The order of middleware is important: the first middleware on the list wraps all others, while the last middleware is the innermost one. @see github.com/technoweenie/faraday#advanced-middleware-usage @see mislav.uniqpath.com/2011/07/faraday-advanced-http/ @return [Faraday::Builder]
# File lib/twitter/rest/client.rb, line 73 def middleware @middleware ||= Faraday::Builder.new do |builder| # Convert file uploads to Faraday::UploadIO objects builder.use Twitter::REST::Request::MultipartWithFile # Checks for files in the payload builder.use Faraday::Request::Multipart # Convert request params to "www-form-urlencoded" builder.use Faraday::Request::UrlEncoded # Handle error responses builder.use Twitter::REST::Response::RaiseError # Parse JSON response bodies builder.use Twitter::REST::Response::ParseJson # Set Faraday's HTTP adapter builder.adapter Faraday.default_adapter end end
Generated with the Darkfish Rdoc Generator 2.