Serializers (Active Model Serializers) in Ruby on Rails - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a serializer class for a User model.

Ruby on Rails

class UserSerializer < ActiveModel::Serializer
  attributes [1]
end

Drag options to blanks, or click blank then click option'

A:id, :name, :email

Bid, name, email

C[:id, :name, :email]

D'id', 'name', 'email'

Attempts:

3 left

💡 Hint

Common Mistakes

Using strings instead of symbols for attribute names.

Passing an array instead of a list of symbols.

The attributes method takes a list of symbols representing the model's fields to include in the serialized output.

2fill in blank

medium

Complete the code to add a custom method attribute to the serializer.

Ruby on Rails

class UserSerializer < ActiveModel::Serializer
  attributes :id, :name, :email, [1]

  def [1]
    object.name.upcase
  end
end

Drag options to blanks, or click blank then click option'

Aupcase_name

Buppercase_name

Cname_upper

Dname_caps

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatch between attribute name and method name.

Using invalid Ruby method names.

The custom attribute name must match the method name defined in the serializer.

3fill in blank

hard

Fix the error in the serializer to correctly include an association.

Ruby on Rails

class UserSerializer < ActiveModel::Serializer
  attributes :id, :name
  has_many [1]
end

Drag options to blanks, or click blank then click option'

A:posts

Bposts

Cpost

D:post

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the colon before the association name.

Using singular form for a has_many association.

Associations must be specified as symbols with the correct pluralization for collections.

4fill in blank

hard

Fill both blanks to define a belongs_to association with a custom serializer.

Ruby on Rails

class CommentSerializer < ActiveModel::Serializer
  attributes :id, :content
  belongs_to [1], serializer: [2]
end

Drag options to blanks, or click blank then click option'

A:user

BUserSerializer

C:post

DPostSerializer

Attempts:

3 left

💡 Hint

Common Mistakes

Using string instead of symbol for association name.

Passing serializer name as a string instead of a constant.

The belongs_to association uses the symbol for the related model and the serializer class name for custom serialization.

5fill in blank

hard

Fill in the blanks to create a serializer with conditional attributes and a custom method.

Ruby on Rails

class ProductSerializer < ActiveModel::Serializer
  attributes :id, :name, [1]

  attribute :discounted_price, if: -> { [2] }

  def discounted_price
    object.price * 0.9
  end
end

Drag options to blanks, or click blank then click option'

A:price

Bobject.on_sale?

Cobject.in_stock?

D:stock

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect attribute names.

Wrong condition lambda syntax.

The attributes list includes :price. The conditional attribute uses a lambda checking object.on_sale?.

Practice

1. What is the main purpose of using Active Model Serializers in a Rails application?

easy

A. To handle database migrations automatically

B. To format and control how Rails models are converted to JSON responses

C. To manage user authentication and sessions

D. To style HTML views with CSS

Solution

1. Step 1: Understand the role of serializers

   Serializers format model data into JSON, deciding which attributes to include.

2. Step 2: Compare with other options

   Database migrations, authentication, and styling are unrelated to serializers.

3. Final Answer:

   To format and control how Rails models are converted to JSON responses -> Option B

4. Quick Check:

   Serializers format JSON = A [OK]

Hint: Serializers shape JSON output, not database or styling [OK]

Common Mistakes:

• Confusing serializers with database migration tools
• Thinking serializers handle user login
• Assuming serializers style HTML pages

2. Which of the following is the correct way to define attributes in an Active Model Serializer?

easy

A. attributes :id, :name, :email

B. attribute :id, :name, :email

C. attrs :id, :name, :email

D. fields :id, :name, :email

Solution

1. Step 1: Recall the syntax for attributes in serializers

   The correct method is attributes followed by symbols for each field.

2. Step 2: Check other options

   attribute (singular), attrs, and fields are not valid methods in Active Model Serializers.

3. Final Answer:

   attributes :id, :name, :email -> Option A

4. Quick Check:

   Use plural 'attributes' method [OK]

Hint: Use plural 'attributes' to list fields in serializer [OK]

Common Mistakes:

• Using singular 'attribute' instead of 'attributes'
• Trying non-existent methods like 'attrs' or 'fields'
• Forgetting to use symbols for attribute names

3. Given this serializer:

class UserSerializer < ActiveModel::Serializer
  attributes :id, :name
  attribute :email
end

What will be the JSON output keys for a user with id=1, name='Alice', email='[e-mail]'?

medium

A. {"id":1,"name":"Alice"}

B. {"id":1,"name":"Alice","email":"[e-mail]"}

C. {"id":1,"name":"Alice", "email":null}

D. NoMethodError due to 'attribute' usage

Solution

1. Step 1: Check serializer attribute methods

   The serializer uses attributes (plural) and attribute (singular). Only attributes is valid; attribute is not a defined method and raises NoMethodError when the class is defined.

2. Step 2: Determine output keys

   The serializer class fails to load due to the undefined method, preventing JSON output.

3. Final Answer:

   NoMethodError due to 'attribute' usage -> Option D

4. Quick Check:

   Undefined 'attribute' method causes error = D [OK]

Hint: Only use plural 'attributes' to include fields [OK]

Common Mistakes:

• Using singular 'attribute' which causes NoMethodError
• Expecting all fields to appear despite syntax error
• Confusing attribute method names

4. Identify the error in this serializer code:

class PostSerializer < ActiveModel::Serializer
  attributes :id, :title

  def title
    object.title.upcase
  end

  def author_name
    object.author.name
  end
end

medium

A. Missing :author_name in attributes list, so it won't appear in JSON

B. Method 'title' should not be defined in serializer

C. Using 'object' is invalid inside serializer methods

D. Attributes list should include :author instead of :author_name

Solution

1. Step 1: Check attributes declaration

   Only :id and :title are declared in attributes, so only these keys appear in JSON.

2. Step 2: Check custom method usage

   Method author_name exists but is not listed in attributes, so it won't be serialized.

3. Final Answer:

   Missing :author_name in attributes list, so it won't appear in JSON -> Option A

4. Quick Check:

   Only declared attributes appear in JSON = B [OK]

Hint: Add custom methods to attributes list to include them [OK]

Common Mistakes:

• Defining methods but forgetting to list them in attributes
• Thinking all methods auto-serialize
• Misusing 'object' inside serializer methods

5. You want to include a nested association in your JSON output using Active Model Serializers. Given these models:

class Article < ApplicationRecord
  belongs_to :author
end

class Author < ApplicationRecord
  has_many :articles
end

And these serializers:

class ArticleSerializer < ActiveModel::Serializer
  attributes :id, :title
  belongs_to :author
end

class AuthorSerializer < ActiveModel::Serializer
  attributes :id, :name
end

What will the JSON output for an article include regarding the author?

hard

A. The author will not be included unless manually added in controller

B. Only the author's id will be included as a number

C. The author will be included as a nested JSON object with :id and :name

D. The JSON will raise an error due to missing author attributes

Solution

1. Step 1: Understand belongs_to in serializer

   Using belongs_to :author in ArticleSerializer includes the author association serialized by AuthorSerializer.

2. Step 2: Check AuthorSerializer attributes

   AuthorSerializer defines :id and :name, so these fields appear nested inside article JSON.

3. Final Answer:

   The author will be included as a nested JSON object with :id and :name -> Option C

4. Quick Check:

   belongs_to includes nested object = C [OK]

Hint: Use belongs_to with serializer to nest associated objects [OK]

Common Mistakes:

• Expecting only author id without serializer
• Thinking associations need manual controller inclusion
• Assuming missing attributes cause errors