13

Say I have a model User and a serializer UserSerializer < ActiveModel::Serializer, and a controller that looks like this:

class UsersController < ApplicationController
  respond_to :json
  def index
    respond_with User.all
  end
end

Now if I visit /users I'll get a JSON response that looks like this:

{
  "users": [
    {
      "id": 7,
      "name": "George"
    },
    {
      "id": 8,
      "name": "Dave"
    }
    .
    .
    .
  ]
}

But what if I want to include some extra information in the JSON response that isn't relevant to any one particular User? E.g.:

{
  "time": "2014-01-06 16:52 GMT",
  "url": "http://www.example.com", 
  "noOfUsers": 2,
  "users": [
    {
      "id": 7,
      "name": "George"
    },
    {
      "id": 8,
      "name": "Dave"
    }
    .
    .
    .
  ]
}

This example is contrived but it's a good approximation of what I want to achieve. Is this possible with active model serializers? (Perhaps by subclassing ActiveModel::ArraySerializer? I couldn't figure it out). How do I add extra root elements?

GMA
  • 5,816
  • 6
  • 51
  • 80

4 Answers4

11

You can pass them as the second arguement to respond_with

def index
 respond_with User.all, meta: {time: "2014-01-06 16:52 GMT",url: "http://www.example.com", noOfUsers: 2}
end

In version 0.9.3 in an initializer set ActiveModel::Serializer.root = true:

ActiveSupport.on_load(:active_model_serializers) do
  # Disable for all serializers (except ArraySerializer)
  ActiveModel::Serializer.root = true
end

In controller

render json: @user,  meta: { total: 10 }
Jason Noble
  • 3,756
  • 19
  • 21
junil
  • 758
  • 5
  • 12
  • This works for me on ActiveModelSerializers 0.8.1. See https://github.com/rails-api/active_model_serializers/blob/0-8-stable/lib/active_model/array_serializer.rb#L41. Looks like this has changed in master, see https://github.com/rails-api/active_model_serializers/blob/78cceb4113c35cddb8cbef42742dc8a7f4cebbb8/lib/active_model/serializable.rb – aceofspades Feb 09 '14 at 20:22
  • Also note this is for arrays only, if you want metadata in an instance, set call `#meta=` on the Serializer instance itself. – aceofspades Feb 09 '14 at 21:31
4

Got it working using render:

render json: {
  "time": "2014-01-06 16:52 GMT",
  "url": "http://www.example.com", 
  "noOfUsers": 2,
  "users": @users
}

The problem is, this doesn't call UserSerializer, it just calls .as_json on each individual user object and skips the Serializer. So I had to do it explicitly:

def index
  .
  .
  .
  render json: {
    "time": "2014-01-06 16:52 GMT",
    "url": "http://www.example.com", 
    "noOfUsers": 2,
    "users": serialized_users
  }
end

def serialized_users
  ActiveModel::ArraySerializer.new(@users).as_json
end

Not the most elegant solution but it works.

GMA
  • 5,816
  • 6
  • 51
  • 80
0

Just a simple hack if you don't want to modify either the serializer or render:

data = serializer.new(object, root: false)
# cannot modify data here since it is a serializer class
data = data.as_json
# do whatever to data as a Hash and pass the result for render
data[:extra] = 'extra stuff'
render json: data
paradite
  • 6,238
  • 3
  • 40
  • 58
0

I was able to get this working for my use case by just adding the following in my controller. Nothing else needed with AMS 0.10.

render 
    json: @user,  
    meta: {
        time: "2014-01-06 16:52 GMT", 
        url: "http://www.example.com", 
        noOfUsers: 2
    }
Dez
  • 5,702
  • 8
  • 42
  • 51
Scott
  • 1