You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using integers for the request seems sensible, although it might get to a point where you want to make a custom type for HTTP request types. It would be nice to be able to give the url but also be able to give protocol. E.g.
The reason that's nice is so that it can be set programmatically more easily. I also think it makes sense to put the method first or, if omitted, default to GET.
Integers for the HTTP method seems fine, but as far as protocol goes, this library's scope is only HTTP/S requests. If it turns out we need more than those two protocols we can add another method to request().
I also like the method first.
request(POST, "http://duckduckgo.com", {"q"=>"hacker school"})
request("https://google.com") # implicit GET
Something similar to Python's Requests would be nice.
The text was updated successfully, but these errors were encountered: