Lucas Hosseini
Lucas Hosseini
@dawidof is the new maintainer
Note: this benchmark is faulty since some legacy AMS idiosyncrasy made it so that the cached serializer _actually_ did twice the work. Could you re-run @bf4?
@GCorbel Caching will only improve performance when serializing objects with computation-heavy attributes. I'm not aware of the current status of it though, although last I heard @bf4 had fixed it.
@mrsweaters Do you have overridden attributes that are costly to compute?
I think you are referring to [these docs](https://github.com/rails-api/active_model_serializers/blob/master/docs/howto/add_relationship_links.md#links-as-an-attribute-of-a-resource) which are wrong (the spec does not allow an attribute named links).
@michael-reeves I wouldn't be sure – the `link` block is `instance_eval`'d in a specific context where some url helpers appear to be mixed in.
@michael-reeves Note that you could simply mix the helper in `ActiveModel::Serializer`: ```ruby class ActiveModel::Serializer include Rails.application.routes.url_helpers end ```
@oyeanuj Not that I know of, no :/
@oyeanuj I'm afraid it will have to come from the community as: + AFAIK, no current maintainer has much experience with 0.9 (or 0.8 for that matter), and + focus...
IMO the reason for this behavior is poor design. A possible fix would be for AMS to automatically define a dummy method that just forwards to the object whenever an...