Alexander Brandon Coles

Hi @fran-worley. Can you post the exact arguments? Note also that the option is `include` not `included`: http://www.rubydoc.info/gems/roar-jsonapi/Roar%2FJSON%2FJSONAPI%2FDocument:to_hash

@fran-worley if you're able to provide a reproduction (or at least the representers), that would help. Otherwise I'll try to reproduce this on the weekend.

@fran-worley I believe this is an issue with hyphenation: `feature-image` relationship name vs. `feature_image` method name, although I'm surprised it isn't affecting single representers as well. I would suspect that...

_From @apotonick on November 25, 2015 2:28_ Does `represented` work for you? That's the official API!

_From @matheusca on November 27, 2015 17:35_ I can't use `represented` as `requester` inside of `has_one` block, because when I used it, the `represented` is the instance of `residence_address` like...

_From @apotonick on December 1, 2015 1:41_ That is correct behaviour. The `represented` method refers to the currently rendered object, which is a `residence_address` in your case. You can do...

_From @apotonick on December 1, 2015 2:21_ As this might be a common problem in JSON API, we _could_ introduce a `:parent_represented` option, which'd work as follows. ``` ruby link...

@Kris-LIBIS could you post your Representer? I'm assuming you have a block that looks something like this? ```ruby link :self, toplevel: true do |options| "/api/organizations?page=#{options[:page]}&per_page=#{options[:per_page]}" end ```

_From @lasseebert on April 15, 2016 8:40_ I have run into the same issue. I have a polymorphic relation: An `AccountUser` has one `Account` which can be one of several...

_From @lasseebert on April 15, 2016 9:23_ I have messed around in the roar code and solved this so that `type` now accepts both a string and a block (mutually...