Nick Sutterer comments

Results 675 comments of


                                            Nick Sutterer

Creating arbitrary hash on lonely collection and encapsulating collection items

Yeah, you're right! I'm an idiot, I was telling you _not_ to use `Collection` and then left it in the code snippet... :stuck_out_tongue_winking_eye:

Creating arbitrary hash on lonely collection and encapsulating collection items

This module, yes, is only for lonely collections, and, no, I'm not gonna rename it, as it is well documented here: https://github.com/apotonick/representable/#lonely-collections :stuck_out_tongue_closed_eyes: Using the `Collection` module in arbitrary representers...

Creating arbitrary hash on lonely collection and encapsulating collection items

Maybe we should note in the README that as soon as you want "more" (e.g. hypermedia) in a lonely collection, you should switch to a non-lonely representer?

With Feature::Client, allow to react to Non-Success HTTP responses to the http-verbs (get, put, post ...)

Ok, good to see you picking up this convo again :smile: What exactly does your added test do, and why is it duplicated in the other PR, too?

With Feature::Client, allow to react to Non-Success HTTP responses to the http-verbs (get, put, post ...)

You have two PRs and they both contain a commit that adds your code to the test server. This should go to one, only. Anyway, thanks a lot! :heart: Can...

With Feature::Client, allow to react to Non-Success HTTP responses to the http-verbs (get, put, post ...)

Here's an idea. ``` ruby object.post!(..) do |response| do_whatever if response.status == 400 end ``` The verb methods with bang (`#post!` and friends) could run the passed block if an...

With Feature::Client, allow to react to Non-Success HTTP responses to the http-verbs (get, put, post ...)

Cool, loving it! So, raise an exception only for specific return statuses?

With Feature::Client, allow to react to Non-Success HTTP responses to the http-verbs (get, put, post ...)

Stupid question, but why do you use Roar and not rest-client? Are you using it for both rendering and consuming (server- or client-side? Or both?)?

With Feature::Client, allow to react to Non-Success HTTP responses to the http-verbs (get, put, post ...)

@paulccarey Cool, that's exactly why I wrote Representers in the first place - no redundancy! Let me get a quick overview about this error handling today, then we (I mean,...

With Feature::Client, allow to react to Non-Success HTTP responses to the http-verbs (get, put, post ...)

Hey guys, can you give me a heads-up, is #109 still the way to go? I am about to release roar-1.0.0.beta1 and this excellent work will defo go into this...