Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to write a Twitter api request to a file in ruby
    primarykey
    data
    text
    <p>Excuse me if this is obvious, I only have about 5 days of experience in ruby. I am trying to write the top 10 trending topics on Twitter to a json file. The API request is a GET request to <a href="https://api.twitter.com/1/trends/1.json" rel="nofollow">https://api.twitter.com/1/trends/1.json</a>. My code is</p> <pre><code>require "net/http" require "uri" require "JSON" uri = URI.parse("https://api.twitter.com/1/trends/1.json") File.open("test.json", "w") do |f| f.write(Net::HTTP.get(uri.host, uri.port)) end </code></pre> <p>Its giving me an error </p> <pre><code>D:/Program Files/ruby-1.9.2/lib/ruby/1.9.1/net/http.rb:1668:in 'initialize': undefined method 'empty?' for 443:Fixnum (NoMethodError) from D:/Program Files/ruby-1.9.2/lib/ruby/1.9.1/net/http.rb:1787:in 'intialize' from D:/Program Files/ruby-1.9.2/lib/ruby/1.9.1/net/http.rb:1081:in 'new' from D:/Program Files/ruby-1.9.2/lib/ruby/1.9.1/net/http.rb:1081:in 'request_get' from D:/Program Files/ruby-1.9.2/lib/ruby/1.9.1/net/http.rb:389:in 'block in get_response' from D:/Program Files/ruby-1.9.2/lib/ruby/1.9.1/net/http.rb:627:in 'start' from D:/Program Files/ruby-1.9.2/lib/ruby/1.9.1/net/http.rb:388:in 'get_response' from D:/Program Files/ruby-1.9.2/lib/ruby/1.9.1/net/http.rb:370:in 'get' from test:8:in 'block in (main)' </code></pre> <p>Any help on this would be great</p> <p>Edit: <a href="https://dev.twitter.com/docs/api/1/get/trends/%3Awoeid" rel="nofollow">https://dev.twitter.com/docs/api/1/get/trends/%3Awoeid</a> is all the info on the API call I am using if I missed providing any important info</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload