Devise gem overview in Ruby on Rails - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add Devise to a Rails model for user authentication.

Ruby on Rails

class User < ApplicationRecord
  [1]
end

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

Ahas_secure_password

Binclude AuthModule

Cdevise :database_authenticatable, :registerable

Dextend Authentication

Attempts:

3 left

💡 Hint

Common Mistakes

Using has_secure_password instead of Devise's devise method.

Forgetting to include any authentication method in the model.

The devise method inside the model sets up authentication modules like database authentication and registration.

2fill in blank

medium

Complete the command to install Devise in a Rails app.

Ruby on Rails

bundle add [1]

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

Apundit

Bdevise

Comniauth

Dcancancan

Attempts:

3 left

💡 Hint

Common Mistakes

Adding unrelated gems like pundit or omniauth instead of Devise.

Forgetting to run bundle install after adding the gem.

The command bundle add devise adds the Devise gem to your Rails project.

3fill in blank

hard

Fix the error in the Devise route setup by completing the blank.

Ruby on Rails

Rails.application.routes.draw do
  [1] :users
end

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

Adevise_for

Bresources

Cget

Droot_to

Attempts:

3 left

💡 Hint

Common Mistakes

Using resources :users which does not set up Devise routes.

Using unrelated routing helpers like get or root_to.

Devise requires devise_for :users in routes to set up authentication paths.

4fill in blank

hard

Fill both blanks to add authentication checks in a controller.

Ruby on Rails

class PostsController < ApplicationController
  before_action [1] :authenticate_user!

  def index
    @posts = Post.all
  end
end

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

Aonly

Bexcept

Cskip_before_action

Dbefore_action

Attempts:

3 left

💡 Hint

Common Mistakes

Using skip_before_action which disables filters instead of adding them.

Confusing except with only.

The before_action :authenticate_user! runs authentication before actions.

5fill in blank

hard

Fill all three blanks to customize Devise's permitted parameters in ApplicationController.

Ruby on Rails

class ApplicationController < ActionController::Base
  before_action [1] :configure_permitted_parameters, if: :devise_controller?

  protected

  def configure_permitted_parameters
    devise_parameter_sanitizer.[2](:sign_up) do |user_params|
      user_params.permit(:email, :password, :password_confirmation, [3])
    end
  end
end

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

Abefore_action

Bpermit

C:username

Dpermit!

Eappend

Fsanitize

Attempts:

3 left

💡 Hint

Common Mistakes

Using permit! which allows all parameters and is unsafe.

Forgetting to check if: :devise_controller? to limit the filter.

Not permitting extra fields like :username.

The before_action calls the method to configure parameters. The permit method allows extra fields like :username during sign up.

Practice

1. What is the primary purpose of the Devise gem in a Rails application?

easy

A. To manage database migrations automatically

B. To add user authentication features like login and registration

C. To style the user interface with CSS

D. To optimize SQL queries for performance

Solution

1. Step 1: Understand Devise's role in Rails

   Devise is a gem designed to handle user authentication tasks such as login, registration, password recovery, and more.

2. Step 2: Compare options with Devise's purpose

   Options B, C, and D relate to database, styling, and optimization, which are not Devise's focus.

3. Final Answer:

   To add user authentication features like login and registration -> Option B

4. Quick Check:

   Devise = User authentication [OK]

Hint: Devise is about user login and registration [OK]

Common Mistakes:

• Confusing Devise with database or styling tools
• Thinking Devise manages database migrations
• Assuming Devise handles UI design

2. Which command correctly installs Devise in a Rails project?

easy

A. rails devise setup

B. rails new devise install

C. rails generate devise:install

D. gem install devise

Solution

1. Step 1: Identify the standard Devise installation command

   The correct command to set up Devise after adding it to the Gemfile is rails generate devise:install.

2. Step 2: Check other options for correctness

   A: rails devise setup is invalid syntax, B: rails new devise install is invalid syntax, C installs the gem globally but not in Rails.

3. Final Answer:

   rails generate devise:install -> Option C

4. Quick Check:

   Devise install command = rails generate devise:install [OK]

Hint: Use 'rails generate devise:install' to set up Devise [OK]

Common Mistakes:

• Using 'gem install devise' instead of Rails generator
• Typing incorrect Rails commands
• Confusing gem installation with setup commands

3. Given the following code snippet in a Rails app using Devise:

class User < ApplicationRecord
  devise :database_authenticatable, :registerable
end

What feature does the :registerable module add to the User model?

medium

A. Allows users to sign up and edit their registration details

B. Encrypts user passwords in the database

C. Enables password reset via email

D. Locks user accounts after failed login attempts

Solution

1. Step 1: Understand the :registerable module

   The :registerable module in Devise adds features for user sign-up, editing, and deleting their account.

2. Step 2: Match other options to correct modules

   Password encryption is handled by :database_authenticatable, password reset by :recoverable, and account locking by :lockable.

3. Final Answer:

   Allows users to sign up and edit their registration details -> Option A

4. Quick Check:

   :registerable = sign up and edit [OK]

Hint: :registerable means users can sign up and edit info [OK]

Common Mistakes:

• Confusing :registerable with password or lock features
• Assuming :registerable encrypts passwords
• Mixing up Devise modules

4. You added Devise to your Rails app and ran rails generate devise User, but you get an error saying uninitialized constant Devise. What is the most likely cause?

medium

A. You ran the generator before creating the User model manually

B. Devise does not support generating User models

C. You need to restart the Rails server before running the generator

D. You forgot to add gem 'devise' to your Gemfile and run bundle install

Solution

1. Step 1: Identify cause of 'uninitialized constant Devise'

   This error usually means the Devise gem is not loaded, often because it was not added to the Gemfile or bundle install was not run.

2. Step 2: Evaluate other options

   The generator creates the User model, so manual creation is not needed. Restarting server does not fix missing gem. Devise supports User model generation.

3. Final Answer:

   You forgot to add gem 'devise' to your Gemfile and run bundle install -> Option D

4. Quick Check:

   Missing gem in Gemfile = uninitialized constant error [OK]

Hint: Add gem and run bundle install before generators [OK]

Common Mistakes:

• Running generator without adding gem to Gemfile
• Assuming User model must exist before generator
• Restarting server without bundling

5. You want to add email confirmation to users signing up with Devise. Which steps should you follow to enable this feature?

hard

A. Add :confirmable to the User model's devise call, generate a migration to add confirmation fields, then run migrations

B. Add :confirmable to the User model and restart the server only

C. Add :confirmable to the User model and create a new controller for confirmations manually

D. Add :confirmable to the User model and update the routes file with confirmation paths

Solution

1. Step 1: Enable :confirmable in User model

   Add :confirmable to the list of Devise modules in the User model to activate confirmation features.

2. Step 2: Add confirmation fields via migration

   Generate and run a migration to add necessary database columns like confirmation_token and confirmed_at.

3. Step 3: Run database migrations

   Run rails db:migrate to apply changes so Devise can track confirmations.

4. Final Answer:

   Add :confirmable to the User model's devise call, generate a migration to add confirmation fields, then run migrations -> Option A

5. Quick Check:

   :confirmable + migration + migrate = email confirmation [OK]

Hint: Add :confirmable and migrate database to enable confirmation [OK]

Common Mistakes:

• Forgetting to create and run migration for confirmation fields
• Assuming adding :confirmable alone is enough
• Manually creating controllers unnecessarily