Gemfile for project dependencies in Ruby - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the source for gems in a Gemfile.

Ruby

source [1]

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

A"https://google.com"

B"http://example.com"

C"gemsource"

D"https://rubygems.org"

Attempts:

3 left

💡 Hint

Common Mistakes

Using an incorrect or non-existent URL as the source.

Forgetting the quotes around the URL.

The source line in a Gemfile tells Bundler where to look for gems. The official RubyGems source is "https://rubygems.org".

2fill in blank

medium

Complete the code to add the 'rails' gem with version '~> 7.0' in the Gemfile.

Ruby

gem 'rails', [1]

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

A'~> 7.0'

B'= 7.0'

C'>= 7.0'

D'< 7.0'

Attempts:

3 left

💡 Hint

Common Mistakes

Using '=' which locks to exactly that version.

Using '<' which restricts to lower versions.

The ~> operator means 'compatible with version', so '~> 7.0' allows updates that do not change the major version.

3fill in blank

hard

Fix the error in the Gemfile line to add the 'nokogiri' gem only for the development group.

Ruby

group :development do
  gem [1]
end

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

A'nokogiri', '~> 1.13'

B'nokogiri', group: :development

C'nokogiri'

D'nokogiri', require: false

Attempts:

3 left

💡 Hint

Common Mistakes

Adding group option inside the group block causing redundancy.

Forgetting to put the gem name in quotes.

Inside a group :development do ... end block, you only need to specify the gem name. The group is already set by the block.

4fill in blank

hard

Fill both blanks to add the 'rspec' gem only for the test group with version '~> 3.10'.

Ruby

group [1] do
  gem 'rspec', [2]
end

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

A:test

B'~> 3.10'

D:development

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong group symbol like :development.

Omitting quotes around the version string.

The group :test do ... end block scopes gems to the test environment. The version string '~> 3.10' specifies compatible versions starting from 3.10.

5fill in blank

hard

Fill all three blanks to add the 'pg' gem for production group with version '>= 1.2', and disable automatic require.

Ruby

group [1] do
  gem 'pg', [2], [3]
end

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

A:production

Brequire: false

C>= '1.2'

D'>= 1.2'

Attempts:

3 left

💡 Hint

Common Mistakes

Using unquoted version strings.

Placing options in wrong order or syntax.

The group :production do ... end block scopes gems to production. The version string '>= 1.2' specifies minimum version 1.2. The option require: false disables automatic loading of the gem.

Practice

1. What is the main purpose of a Gemfile in a Ruby project?

easy

A. To configure the web server

B. To write Ruby program logic

C. To store database credentials

D. To list all the gems the project depends on

Solution

1. Step 1: Understand the role of Gemfile

   A Gemfile is used to specify which gems (libraries) a Ruby project needs to work properly.

2. Step 2: Compare options with Gemfile purpose

   Only To list all the gems the project depends on correctly states that Gemfile lists project gem dependencies.

3. Final Answer:

   To list all the gems the project depends on -> Option D

4. Quick Check:

   Gemfile purpose = list gems [OK]

Hint: Gemfile lists gems needed for the project [OK]

Common Mistakes:

• Confusing Gemfile with Ruby code files
• Thinking Gemfile stores secrets or configs
• Assuming Gemfile runs the program

2. Which line is the correct syntax to add the gem 'rails' version 7.0.0 in a Gemfile?

easy

A. gem 'rails', '7.0.0'

B. gem rails, '7.0.0'

C. gem 'rails' version '7.0.0'

D. gem 'rails' => '7.0.0'

Solution

1. Step 1: Recall Gemfile gem syntax

   The correct syntax uses the keyword gem, gem name in quotes, then version as a string separated by a comma.

2. Step 2: Check each option

   gem 'rails', '7.0.0' matches the correct syntax: gem 'rails', '7.0.0'. Others have syntax errors or wrong keywords.

3. Final Answer:

   gem 'rails', '7.0.0' -> Option A

4. Quick Check:

   Gemfile gem syntax = gem 'name', 'version' [OK]

Hint: Use gem 'name', 'version' format in Gemfile [OK]

Common Mistakes:

• Omitting quotes around gem name
• Using => instead of comma for version
• Writing version without quotes

3. Given this Gemfile snippet:

source 'https://rubygems.org'
gem 'nokogiri', '~> 1.12.0'
gem 'puma', '5.0'

What happens when you run bundle install?

medium

A. Installs latest versions of nokogiri and puma

B. Installs nokogiri version exactly 1.12.0 and puma latest version

C. Installs nokogiri version 1.12.x and puma version 5.0

D. Throws an error due to invalid version syntax

Solution

1. Step 1: Understand version specifiers in Gemfile

   ~> 1.12.0 means any version >=1.12.0 and <1.13.0 (patch updates allowed). '5.0' means exactly version 5.0.

2. Step 2: Interpret bundle install behavior

   Bundle installs nokogiri in 1.12.x range and puma exactly 5.0, matching Installs nokogiri version 1.12.x and puma version 5.0.

3. Final Answer:

   Installs nokogiri version 1.12.x and puma version 5.0 -> Option C

4. Quick Check:

   ~> means compatible version, exact string means exact version [OK]

Hint: ~> means compatible version, exact string means exact version [OK]

Common Mistakes:

• Thinking '~>' means exact version
• Assuming '5.0' means latest version
• Confusing version operators

4. Identify the error in this Gemfile snippet:

source 'https://rubygems.org'
gem 'rails', '6.1.4'
gem 'pg', '~> 1.2.3'
gem 'puma' '5.0'

medium

A. Missing comma between gem name and version in last line

B. Incorrect source URL

C. Version numbers are invalid

D. Gem 'pg' version specifier is wrong

Solution

1. Step 1: Check syntax of each gem line

   Each gem line should have a comma between gem name and version string.

2. Step 2: Locate the error

   Last line has gem 'puma' '5.0' missing a comma between 'puma' and '5.0'.

3. Final Answer:

   Missing comma between gem name and version in last line -> Option A

4. Quick Check:

   Gemfile gem syntax requires comma [OK]

Hint: Check commas between gem name and version [OK]

Common Mistakes:

• Omitting commas between gem name and version
• Assuming source URL is incorrect
• Misreading version specifiers

5. You want to add a gem only for the development environment in your Gemfile. Which is the correct way to do this?

hard

A. gem 'pry', environment: 'development'

B. group :development do
gem 'pry'
end

C. gem 'pry' if ENV['RACK_ENV'] == 'development'

D. group 'development' gem 'pry' end

Solution

1. Step 1: Recall how to specify environment groups in Gemfile

   Use group :environment_name do ... end block to add gems for specific environments.

2. Step 2: Evaluate each option

   group :development do gem 'pry' end correctly uses group :development do ... end syntax. Others are invalid Ruby or Gemfile syntax.

3. Final Answer:

   group :development do gem 'pry' end -> Option B

4. Quick Check:

   Use group blocks for environment-specific gems [OK]

Hint: Use group :env do ... end for environment gems [OK]

Common Mistakes:

• Trying to add environment as gem option
• Using if conditions inside Gemfile
• Incorrect group block syntax