Daniel (dB.) Doubrovkine
Daniel (dB.) Doubrovkine
> do these make sense? sorry for the confusion, and the delay! (tbh, I was only evaluating IEX when I authored this PR, and have since switched gears to another...
@rodolfobandeira has been adding a lot I wonder if this strategy is too tedious and we should auto-generate this code. Worth looking at how https://github.com/slack-ruby/slack-ruby-client does it.
I am generally against dynamic wrapping, which can be done without this client for the most part. One of the main goals of writing this gem was to validate parameters...
First try getting a machine readable version of the IEX API. Maybe they have a swagger doc or something like that. Then try to list all methods and fields. Then...
Please feel free to PR!
There's a fix for #79 in #71.
I released 1.2.0.
> Any plans to implement this? Looking up company data one at a time is a bottleneck for the application I'm writing. Please contribute.
Do we want to raise errors in Grape for this? Feels like that would be a no, because a contract is a contract, but I'm open to it.
@ebenoist Care to dig up whether this is the case un latest Rack and what the Rack API is supposed to be? Seems like there's no conclusion above.