Error messages and display in Ruby on Rails - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of errors.full_messages in Rails?

It collects all error messages from a model's validation failures into an array of readable strings, which can be shown to users.

beginner

How do you display error messages for a specific attribute in a Rails form?

Use object.errors[:attribute] to get errors for that attribute and display them near the form field.

intermediate

What helper method can you use in Rails views to show all errors for a model?

You can build a custom partial that iterates over @model.errors.full_messages. Note: error_messages_for was deprecated and removed in Rails 3.

beginner

Why is it important to display error messages near the related form fields?

It helps users quickly understand what needs fixing, improving user experience and reducing frustration.

intermediate

How can you customize error message text in Rails validations?

You can pass the :message option to validation helpers like validates :name, presence: { message: 'must be given' }.

Which method returns all error messages as an array of strings in Rails?

A errors.list

B errors.full_messages

C errors.to_s

D errors.messages

errors.full_messages returns all error messages in a user-friendly format.

Where should you display error messages in a form for best user experience?

A Near the related form fields

B In the browser console

C At the top of the page only

D In a popup alert

Showing errors near the related fields helps users fix issues quickly.

How do you customize the error message for a presence validation in Rails?

A By editing the locale file only

B By changing the database schema

C By overriding <code>to_s</code> method

D Using the <code>:message</code> option in the validation

You can pass :message to validation helpers to customize error text.

What does object.errors[:attribute] return?

A The number of errors

B All errors for the object

C Error messages for a specific attribute

D The validation rules

This returns an array of error messages for the given attribute.

Which Rails feature automatically adds errors to a model after validation fails?

A ActiveModel validations

B ActiveRecord callbacks

C ActionController filters

D ActiveJob background jobs

ActiveModel validations add errors to the model when validations fail.

Explain how Rails handles error messages when a form submission fails validation.

Think about what happens after you try to save a model with invalid data.

Describe best practices for showing error messages in a Rails web form.

Consider how to help users fix mistakes easily.

Practice

1. In Rails, which method provides a list of user-friendly error messages for a model's validation errors?

easy

A. @model.errors.count

B. @model.errors.details

C. @model.errors.keys

D. @model.errors.full_messages

Solution

1. Step 1: Understand error message methods

   @model.errors.full_messages returns an array of readable error strings, while others return metadata or counts.

2. Step 2: Identify user-friendly output

   Only full_messages gives clear, complete error messages suitable for display.

3. Final Answer:

   @model.errors.full_messages -> Option D

4. Quick Check:

   Error messages = full_messages [OK]

Hint: Use full_messages for readable error text [OK]

Common Mistakes:

• Using errors.details which gives error codes, not messages
• Using errors.keys which lists fields, not messages
• Using errors.count which returns number, not messages

2. Which of the following is the correct way to display error messages for a @user model in a Rails view?

easy

A. <%= @user.errors.full_messages.each do |msg| %> <%= msg %> <% end %>

B. <% @user.errors.full_messages.each do |msg| %> <%= msg %> <% end %>

C. <%= @user.errors.full_messages.map { |msg| content_tag(:p, msg) } %>

D. <% @user.errors.full_messages.map { |msg| content_tag(:p, msg) } %>

Solution

1. Step 1: Understand ERB tags for iteration

   <% %> runs Ruby code without output; <%= %> outputs the result. For loops, use <% %>.

2. Step 2: Identify correct syntax for displaying messages

   <% @user.errors.full_messages.each do |msg| %>

   <%= msg %>

   <% end %> correctly uses <% %> to loop and <%= %> inside to output each message.

3. Final Answer:

   Option B -> Option B

4. Quick Check:

   Loop with <% %>, output with <%= %> [OK]

Hint: Use <% %> for loops, <%= %> for output inside loops [OK]

Common Mistakes:

• Using <%= %> for loops causing unwanted output
• Using map without outputting results
• Mixing output and code tags incorrectly

3. Given this Rails code in a view:

<ul>
  <% @post.errors.full_messages.each do |msg| %>
    <li><%= msg %></li>
  <% end %>
</ul>

What will be the output if @post.errors.full_messages contains ["Title can't be blank", "Content is too short"]?

medium

A. Title can't be blankContent is too short

B. Title can't be blankContent is too short

C. Title can't be blankContent is too short

D. No output because of syntax error

Solution

1. Step 1: Understand the loop output

   The code loops over each error message and wraps it in
2. tags inside a <ul>.

3. Step 2: Match output to HTML structure

   The output will be a <ul> list with two
4. items showing each error message.

5. Final Answer:

   <ul><li>Title can't be blank</li><li>Content is too short</li></ul> -> Option A

6. Quick Check:

   Loop creates list items inside ul [OK]

Hint: Errors inside <li> tags within <ul> show as list [OK]

Common Mistakes:

• Forgetting <ul> tags causing invalid HTML
• Not using <li> tags for each message
• Confusing output with plain text

4. You wrote this code to display errors:

<%= @article.errors.full_messages.each do |msg| %>
  <p><%= msg %></p>
<% end %>

But no errors show up in the browser. What is the problem?

medium

A. The <code><p>s

B. You must call to_s on each message before displaying

C. Using <code><%= %>s

D. The errors array is empty, so nothing shows

Solution

1. Step 1: Check ERB tag usage for loops

   Using <%= %>each, which is the original array, not the loop content.

2. Step 2: Correct loop tag usage

   Use <% %> for loops to run code without output, then use <%= %> inside for each message.

3. Final Answer:

   Using <%= %> for the loop causes output of the array, not the messages -> Option C

4. Quick Check:

   Use <% %> for loops, not <%= %> [OK]

Hint: Use <% %> for loops, <%= %> for output inside loops [OK]

Common Mistakes:

• Using <%= %> for loops causing wrong output
• Assuming errors are empty without checking
• Misunderstanding HTML tag usage inside loops

5. You want to display error messages only if there are any errors on the @comment model. Which is the best way to do this in a Rails view?

hard

A. <% if @comment.errors.any? %>
<div role='alert' aria-live='assertive'>
<ul>
<% @comment.errors.full_messages.each do |msg| %>
<li><%= msg %></li>
<% end %>
</ul>
</div>
<% end %>

B. <div>
<ul>
<% @comment.errors.full_messages.each do |msg| %>
<li><%= msg %></li>
<% end %>
</ul>
</div>

C. <% if @comment.errors.count > 0 %>
<p>Errors found</p>
<% end %>

D. <% unless @comment.errors.empty? %>
<p>Please fix errors</p>
<% end %>

Solution

1. Step 1: Check for errors presence

   Use errors.any? to check if there are any errors to display.

2. Step 2: Display errors accessibly

   Wrap errors in a div with role='alert' and aria-live='assertive' for screen readers to announce changes.

3. Step 3: Loop and show messages

   Use full_messages inside a ul with li for each error message.

4. Final Answer:

   Option A -> Option A

5. Quick Check:

   Check errors.any? and use accessible alert div [OK]

Hint: Use errors.any? and role='alert' div for accessible errors [OK]

Common Mistakes:

• Not checking if errors exist before displaying
• Missing accessibility roles for error containers
• Displaying generic messages without details