Error messages and display in Ruby on Rails - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

How does Rails display validation errors in a form?

Given a Rails form with a model that has validation errors, how does the form_with helper display these errors by default?

A It logs the errors to the server console but does not display anything on the form.

B It highlights the input fields with errors but does not show any error messages.

C It redirects the user to a separate error page showing all validation errors.

D It automatically adds a <code>div</code> with <code>id='error_explanation'</code> containing a list of error messages above the form.

💡 Hint

Think about what Rails helpers do automatically when validations fail.

Rails form_with automatically generates a div with id='error_explanation' that lists all validation errors above the form fields, making it easy for users to see what went wrong.

📝 Syntax

intermediate

Correct syntax to display error messages for a specific attribute

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

A <%= @user.errors.full_messages_for(:email).join(", ") %>

B <%= @user.errors[:email].full_messages.join(", ") %>

C <%= @user.errors.messages_for(:email).join(", ") %>

D <%= @user.errors.get_messages(:email).join(", ") %>

💡 Hint

Look for the method that returns full error messages for a specific attribute.

The method full_messages_for(:attribute) returns an array of full error messages for that attribute. The other options either use incorrect method names or call methods on wrong objects.

🔧 Debug

advanced

Why are error messages not showing in the form?

A developer notices that after submitting a form with invalid data, the error messages are not displayed, even though validations fail. The form uses form_with model: @user. What is the most likely cause?

A The form uses <code>form_tag</code> instead of <code>form_with</code>.

B The model does not have any validations defined.

C The controller action does not re-render the form view on validation failure, but redirects instead.

D The database schema does not have the required columns.

💡 Hint

Think about what happens after a failed save in the controller.

If the controller redirects after a failed save, the error messages stored in the model instance are lost. To display errors, the controller should re-render the form view with the invalid model instance.

❓ state_output

advanced

What is the content of flash[:error] after a failed save?

In a Rails controller, after if @user.save fails, the developer sets flash[:error] = @user.errors.full_messages.join(", "). What will flash[:error] contain?

A A hash of attribute names and error messages.

B A single string with all error messages joined by commas.

C An array of error messages.

D An empty string because errors are not saved in flash.

💡 Hint

Consider what join does to an array.

The full_messages method returns an array of strings. Using join(", ") converts this array into a single string with messages separated by commas.

🧠 Conceptual

expert

Why use errors.add in custom validation methods?

In Rails, when writing a custom validation method inside a model, why do we use errors.add(:attribute, "message") instead of just raising an exception?

A Because <code>errors.add</code> collects errors to show in the form without stopping execution, while raising an exception halts the process.

B Because raising exceptions is deprecated in Rails validations.

C Because <code>errors.add</code> automatically fixes the invalid data.

D Because raising exceptions only works in controllers, not models.

💡 Hint

Think about user experience and how validations should behave.

Using errors.add allows Rails to collect all validation errors and display them to the user without stopping the program. Raising exceptions would interrupt the normal flow and is not suitable for validations.