Nick Sutterer

@eliten00b @elShiaLabeouf Here's a rough outlook of how I envision the interface: https://github.com/trailblazer/trailblazer-endpoint/blob/master/test/matcher_test.rb#L17 - it will look slightly less clumsy in a controller. Any comments here? :beers:

@eliten00b Interesting! A custom output has never been a "failure" per definition, that's why we gave it an attribute "semantic". It's up to the user to decide what "not_found" means....

@eliten00b Good point! Let me finalize my code over here and then we can discuss the API for `endpoint`. :coffee:

It's not bound to any framework at all, so should be fine with Rails. I'd love to rebrush it a bit, thou. Not sure if I like the conventional helper...

First of all: HAPPY NEW YEAR! :fireworks: Currently, Representable compiles the entire collection and then assigns it to the model. We will add another semantic to Representable, but I advise...

``` ruby module SingerRepresenter include Roar::Representer::JSON # should be a switch in the generator for other formats like XML or HTML property :name, :extend => BandRepresenter, :class => Band collection...

:heart: On Mon, Jul 29, 2013 at 10:37 PM, Guilherme Cavalcanti < [email protected]> wrote: > Hey @apotonick https://github.com/apotonick, I'll tackle this one, ok? > I pull request you as soon...

Let's chat here: https://gitter.im/trailblazer/chat :heart:

I remember this problem from a while ago (`undefined method responder='`) but thought we had it fixed. Can you find out where in Rails 4.1 the `#responder=` method is defined?

Does that help? https://github.com/apotonick/roar-rails/issues/87