-
Notifications
You must be signed in to change notification settings - Fork 5
parse the api outputs into correct Ruby objects + some cleanup #1
base: master
Are you sure you want to change the base?
Conversation
Hmm why this? Why not just a simple wrapper? As it is, it's a good intermediary. |
I agree with the idea of a simply wrapper, although I can't really imagine a situation in which somebody would need outputs like: > doge_api.get_my_addresses
=> "[\"DJsRoMLeJxZTSxR9p5tJbUTPyajtUjJRYJ\",\"DFWTu9AggP4erazZQe93FRe51Czxz47bQk\",\"D7uHhk8ZHntySNMaaJ63vXh5omhY3EuBS3\",\"DKYhX9rgwcyTiiiX83pvKtkvpWhPNJsgBd\"]" or: > doge_api.get_balance
=> "\"0\"" |
That's true, but the only reason it's being escaped is because you're not On Sat, Feb 1, 2014 at 10:18 AM, Mariusz [email protected] wrote:
|
You are right, I might misunderstood the intended use of this gem. In my case, I want to call the DogeAPI and get some variables that I could later store (like the list of addresses) or use for processing (account balance, etc.), which means that the outputs I expect need to be integers, floats, strings and arrays. Then I guess I can keep my fork separately and use it when needed, unless maybe you can suggest a better solution for this use case? |
Conflicts: README.md
I think in this case, there could definitely be a flag to parse into Ruby objects. Alternatively, there could be some route grouping by return type (as you proposed)... though I'm not sure I'm fond of the proposed changes in: Questions:
|
wow much revised pls merge