Alexander Brandon Coles

_From @apotonick on April 16, 2016 2:29_ The example @caseymct gives is more complicated, @lasseebert! You only need the `type` dynamic, in the other issue, the entire representer must be...

_From @lasseebert on April 17, 2016 20:45_ @apotonick, yes I see now that my issue is not related at all to the original issue posted here, since dynamically deciding the...

_From @apotonick on January 6, 2015 22:15_ @ekosz Can you add a test to `client_test.rb`? What happens if you include `Roar::JSON` and then `Roar::JSON::JSONAPI`? Feel free to PR fixed README,...

@apotonick we should discuss making `::Declarative::Schema::DSL::NestedBuilder` inherit defaults (same issue as https://github.com/trailblazer/roar/issues/173#issuecomment-161547989, #13)

@twiduch I'm trying to find where in the JSON API docs this behaviour is specified :) > I think that in Json API there should be only one included field...

@patcoll Have you considered using the lower-level [`Roar::JSON::JSONAPI::Mixin`](http://www.rubydoc.info/gems/roar-jsonapi/Roar/JSON/JSONAPI/Mixin) module? ```ruby class DocumentSingleResourceObjectDecorator < Roar::Decorator include Roar::JSON::JSONAPI::Mixin type :articles property :id attributes do property :title end end ``` FWIW I'm not...

This is an issue with Trailblazer 1.1.x (not sure if Trailblazer 2.0 is affected) and not Representable/ROAR JSON API. The `represent` method currently expects an instance of the `Array` class,...

@fran-worley I'd love to merge this - can we convince @apotonick to drop 1.9 support?

For the sake of consistency, this makes sense.

We experienced a similar issue with https://github.com/ducksboard/gridster.js, which can be fixed with this patch: https://github.com/ducksboard/gridster.js/pull/273