CollectionSerializer does not work when serializer is namespaced

[kapso]

Collection serializer does not work when serializer is namespaced inside a module.

So in the following case, it always defaults to just UserSerializer and not Admin::UserSerializer

ActiveModel::Serializer::CollectionSerializer.new(@users, each_serializer: Admin::UserSerializer)

[bf4]

Could you note why you closed this?

[kapso]

I used serializer: instead of each_serializer: and that fixed the issue.

[bf4]

thanks for sharing back! did you find it in the docs? Just interested in your debugging path.

[bf4]

@kapso I also recommend that you do not use the collection serializer directly. That's not how AMS is designed to be used.

[kapso]

@bf4 I had dig into the code for this. I am trying to upgrade from 0.9.3 to 0.10.4 and have been running into few issues and docs are hard to come by for this upgrade :(

Lot of our serializers are namespaced, for e.g. UserSerializer (root namespace), Admin::UserSerializer (under /admin), Api::UserSerializer (under /api)

This used to work in 0.9.3 but errors out in 0.10.4

@users = User.active # or User.active.to_a
render json: @users, serializer: Admin::UserSerializer, root: true

So I am forced to use

render json: {
  users: ActiveModel::Serializer::CollectionSerializer.new(@users, serializer: Admin::UserSerializer)
}

[bf4]

Some related issues C: Upgrading