Model-backed forms in Ruby on Rails - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a form for a model instance named @post.

Ruby on Rails

<%= form_with model: [1] do |form| %>
  <!-- form fields here -->
<% end %>

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

Apost

Bform

CPost.new

D@post

Attempts:

3 left

💡 Hint

Common Mistakes

Using the class name instead of the instance variable.

Using a local variable instead of the instance variable.

The form_with helper uses the model: option with the instance variable @post to create a form tied to that model.

2fill in blank

medium

Complete the code to create a text field for the :title attribute inside the form builder.

Ruby on Rails

<%= form.text_field [1] %>

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

A:date

B:content

C:title

D:author

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong attribute name.

Omitting the colon before the attribute name.

The text_field helper needs the attribute symbol :title to create a text input for that attribute.

3fill in blank

hard

Fix the error in the form helper call to correctly submit the form.

Ruby on Rails

<%= form_with model: @post, [1]: true do |form| %>
  <!-- form fields -->
<% end %>

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

Alocals

Blocal

Clocales

Dlocalize

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'local' without the colon.

Using misspelled keys like 'locales' or 'locals'.

The correct option to make the form submit without a page reload is local: true.

4fill in blank

hard

Fill both blanks to create a label and a text field for the :email attribute.

Ruby on Rails

<%= form.label [1] %>
<%= form.text_field [2] %>

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

A:email

B:name

C:username

D:password

Attempts:

3 left

💡 Hint

Common Mistakes

Using different attributes for label and field.

Forgetting the colon before the attribute name.

Both the label and the text field should use the same attribute symbol :email to connect them properly.

5fill in blank

hard

Fill all three blanks to create a form with a model, a label for :password, and a password field.

Ruby on Rails

<%= form_with model: [1] do |form| %>
  <%= form.label [2] %>
  <%= form.password_field [3] %>
<% end %>

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

A@user

B:password

D:email

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing attribute symbols for label and field.

Using the wrong instance variable for the model.

The form is for the @user model. The label and password field both use the :password attribute symbol.

Practice

1. What is the main advantage of using form_with model: @model in Rails?

easy

A. It creates a form without any connection to the database.

B. It automatically links the form to the model for easy data handling.

C. It disables form validations for faster submission.

D. It generates a plain HTML form without Rails helpers.

Solution

1. Step 1: Understand model-backed forms

   Model-backed forms connect the form fields directly to the model's attributes, simplifying data handling.

2. Step 2: Recognize the role of form_with model: @model

   This helper automatically binds the form to the model instance, enabling validations and error messages.

3. Final Answer:

   It automatically links the form to the model for easy data handling. -> Option B

4. Quick Check:

   Model-backed forms = automatic model connection [OK]

Hint: Remember: model option links form to data model directly [OK]

Common Mistakes:

• Thinking it creates a form without database connection
• Assuming validations are disabled
• Confusing it with plain HTML forms

2. Which of the following is the correct syntax using form_with to create a model-backed form for a @post object in Rails?

easy

A. form_with url: posts_path do |form|

B. form_for @post do |form|

C. form_with model: @post do |form|

D. form_tag @post do |form|

Solution

1. Step 1: Identify the modern Rails form helper

   Rails 5.1+ recommends form_with for forms, replacing older helpers.

2. Step 2: Use the model option for model-backed forms

   Using model: @post binds the form to the @post instance for automatic attribute handling.

3. Final Answer:

   form_with model: @post do |form| -> Option C

4. Quick Check:

   Correct syntax uses form_with + model option [OK]

Hint: Use form_with with model: @object for model forms [OK]

Common Mistakes:

• Using form_tag which is for non-model forms
• Using form_for which is deprecated
• Using url option instead of model for model forms

3. Given the following code snippet, what will be the rendered HTML input name attribute for the title field?

form_with model: @article do |form|
  form.text_field :title
end

medium

A. article[title]

B. title

C. article_title

D. form[title]

Solution

1. Step 1: Understand Rails naming conventions for model-backed forms

   Rails uses the model name as a prefix in input names to group attributes, e.g., modelname[field].

2. Step 2: Apply to the given example

   For model @article and field :title, the input name becomes article[title] to map params correctly.

3. Final Answer:

   article[title] -> Option A

4. Quick Check:

   Input name = model[field] format [OK]

Hint: Input names use model[field] format in model-backed forms [OK]

Common Mistakes:

• Using just the field name without model prefix
• Combining model and field with underscore
• Using form as prefix instead of model name

4. Identify the error in this model-backed form code snippet:

form_with model: @user do |form|
  form.text_field :email
  form.submit
end

The form does not display validation errors when the email is invalid. Why?

medium

A. The form_with helper does not support model-backed forms.

B. The form does not include form.error_messages to show errors.

C. The form is missing local: true to enable validations.

D. The model @user lacks validations on the email attribute.

Solution

1. Step 1: Check if form_with supports model-backed forms

   form_with fully supports model-backed forms and validations automatically.

2. Step 2: Verify model validations

   If validation errors do not show, likely the model @user does not have validations defined for email.

3. Final Answer:

   The model @user lacks validations on the email attribute. -> Option D

4. Quick Check:

   Missing model validations = no errors shown [OK]

Hint: Validation errors need model validations defined [OK]

Common Mistakes:

• Assuming form_with needs local: true for validations
• Expecting form.error_messages helper to exist
• Thinking form_with can't handle model forms

5. You want to create a nested model-backed form where a Project has many Tasks. Which approach correctly handles nested attributes in the form?

hard

A. Use form_with model: @project and inside use form.fields_for :tasks to build task fields.

B. Use separate form_with for @project and each @task without nesting.

C. Use form_tag with manual input names for tasks.

D. Use form_with model: @task only, ignoring the project.

Solution

1. Step 1: Understand nested model forms in Rails

   Rails supports nested attributes allowing a parent model form to include child model fields.

2. Step 2: Use fields_for inside form_with

   To handle nested tasks inside a project form, use form.fields_for :tasks to generate fields for each task.

3. Final Answer:

   Use form_with model: @project and inside use form.fields_for :tasks to build task fields. -> Option A

4. Quick Check:

   Nested forms use fields_for inside form_with [OK]

Hint: Use fields_for inside form_with for nested models [OK]

Common Mistakes:

• Creating separate forms instead of nested
• Using form_tag which lacks model binding
• Ignoring parent model in nested forms