Gem versions and constraints in Ruby - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify a gem version exactly 2.1.0.

Ruby

gem 'rails', '[1]'

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

A'>= 2.1.0'

B'= 2.1.0'

C'~> 2.1.0'

D'< 2.1.0'

Attempts:

3 left

💡 Hint

Common Mistakes

Using '~>' instead of '=' for exact version.

Using '>=' which allows newer versions.

Using '= 2.1.0' means the gem version must be exactly 2.1.0.

2fill in blank

medium

Complete the code to allow any version greater than or equal to 1.5 but less than 2.0.

Ruby

gem 'nokogiri', '[1]'

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

A'~> 1.5'

B'= 1.5'

C['>= 1.5', '< 2.0']

D'> 1.5, <= 2.0'

Attempts:

3 left

💡 Hint

Common Mistakes

Using '~> 1.5' which allows versions up to but not including 2.0 but starting at 1.5.x only.

Using '=' which fixes to one version.

The constraint '>= 1.5, < 2.0' means versions from 1.5 up to but not including 2.0 are allowed.

3fill in blank

hard

Fix the error in the version constraint to allow versions starting from 3.0 up to but not including 4.0.

Ruby

gem 'puma', '[1]'

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

A'>= 3.0, < 4.0'

B'= 3.0'

C'~> 3.0'

D'> 3.0, < 4.0'

Attempts:

3 left

💡 Hint

Common Mistakes

Using '~> 3.0' which allows versions starting at 3.0 but less than 4.0 only if minor version is zero.

Using '> 3.0' which excludes version 3.0 itself.

The correct syntax to allow versions from 3.0 up to but not including 4.0 is '>= 3.0, < 4.0'.

4fill in blank

hard

Fill both blanks to specify a gem version that is at least 2.2 but less than 3.0.

Ruby

gem 'devise', '[1]', '[2]'

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

A'>= 2.2'

B'= 2.2'

C'< 3.0'

D'~> 2.2'

Attempts:

3 left

💡 Hint

Common Mistakes

Using '=' which fixes to one version.

Using '~>' which may allow versions outside the intended range.

Using '>= 2.2' and '< 3.0' together means versions from 2.2 up to but not including 3.0 are allowed.

5fill in blank

hard

Fill all three blanks to specify a gem version that is at least 1.8, less than 2.0, and not equal to 1.9.1.

Ruby

gem 'sidekiq', '[1]', '[2]', '[3]'

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

A'>= 1.8'

B'< 2.0'

C'!= 1.9.1'

D'= 1.9.1'

Attempts:

3 left

💡 Hint

Common Mistakes

Using '=' instead of '!=' to exclude a version.

Not excluding the unwanted version.

Using '>= 1.8', '< 2.0', and '!= 1.9.1' means versions from 1.8 up to but not including 2.0 are allowed except version 1.9.1.

Practice

1. What does the Ruby gem version constraint ~> 2.3.0 mean?

easy

A. It allows versions >= 2.3.0 and < 2.4.0

B. It allows only version 2.3.0 exactly

C. It allows any version greater than 2.3.0

D. It allows versions < 2.3.0

Solution

1. Step 1: Understand the meaning of the pessimistic operator

   The ~> operator means "compatible with" the specified version, allowing updates that do not change the leftmost specified digit.

2. Step 2: Apply to version 2.3.0

   For ~> 2.3.0, it allows versions from 2.3.0 up to but not including 2.4.0.

3. Final Answer:

   It allows versions >= 2.3.0 and < 2.4.0 -> Option A

4. Quick Check:

   ~> 2.3.0 = >= 2.3.0 and < 2.4.0 [OK]

Hint: Remember ~> locks last digit, allows patch updates [OK]

Common Mistakes:

• Thinking ~> means exact version
• Confusing ~> with >= or >
• Assuming it allows major version changes

2. Which of the following is the correct syntax to specify a gem version constraint for versions greater than or equal to 1.5.0 but less than 2.0.0 in a Gemfile?

easy

A. gem 'rails', '== 1.5.0', '< 2.0.0'

B. gem 'rails', '~> 1.5.0', '< 2.0.0'

C. gem 'rails', '> 1.5.0', '<= 2.0.0'

D. gem 'rails', '>= 1.5.0', '< 2.0.0'

Solution

1. Step 1: Understand how to specify multiple version constraints

   In a Gemfile, multiple version constraints are given as separate string arguments after the gem name.

2. Step 2: Check each option's syntax

   gem 'rails', '>= 1.5.0', '< 2.0.0' correctly uses '>= 1.5.0' and '< 2.0.0' as separate strings. gem 'rails', '~> 1.5.0', '< 2.0.0' uses '~>' which is not combined with another constraint properly. gem 'rails', '== 1.5.0', '< 2.0.0' uses '==' which fixes exact version, not a range. gem 'rails', '> 1.5.0', '<= 2.0.0' uses '>' instead of '>=' and '<=' which is incorrect for the requirement.

3. Final Answer:

   gem 'rails', '>= 1.5.0', '< 2.0.0' -> Option D

4. Quick Check:

   Multiple constraints as separate strings = gem 'rails', '>= 1.5.0', '< 2.0.0' [OK]

Hint: Use separate strings for multiple constraints in Gemfile [OK]

Common Mistakes:

• Combining constraints in one string incorrectly
• Using == instead of >= for ranges
• Using wrong operators like > instead of >=

3. Given the Gemfile line gem 'nokogiri', '~> 1.10.0', which of the following versions will Bundler accept when installing?

medium

A. 1.9.0

B. 1.10.5

C. 2.0.0

D. 1.11.0

Solution

1. Step 1: Interpret the '~> 1.10.0' constraint

   This means versions >= 1.10.0 and < 1.11.0 are allowed.

2. Step 2: Check each version against the range

   Version 1.9.0 is less than 1.10.0 (not allowed). 1.10.5 is between 1.10.0 and 1.11.0 (allowed). 2.0.0 is greater than 1.11.0 (not allowed). 1.11.0 is equal to the upper bound (not allowed).

3. Final Answer:

   1.10.5 -> Option B

4. Quick Check:

   ~> 1.10.0 allows 1.10.x but not 1.11.0 [OK]

Hint: ~> locks last digit, allows patch updates only [OK]

Common Mistakes:

• Allowing versions equal to upper bound
• Confusing minor and patch version limits
• Assuming major version updates allowed

4. You have this Gemfile line: gem 'puma', '~> 5.0'. You want to allow updates up to but not including 5.1.0. What is the correct fix?

medium

A. Change to gem 'puma', '~> 5'

B. Change to gem 'puma', '>= 5.0', '< 6.0'

C. Change to gem 'puma', '~> 5.0.0'

D. No change needed, it already allows up to 5.1.0

Solution

1. Step 1: Understand what '~> 5.0' allows

   The constraint '~> 5.0' allows versions >= 5.0.0 and < 6.0.0.

2. Step 2: Apply to the requirement

   To restrict to up to but not including 5.1.0, change to '~> 5.0.0' which allows >= 5.0.0 and < 5.1.0. The other options either keep the loose range or make it invalid.

3. Final Answer:

   Change to gem 'puma', '~> 5.0.0' -> Option C

4. Quick Check:

   ~> 5.0.0 = >= 5.0.0 and < 5.1.0 [OK]

Hint: Add .0 to ~> to lock minor version, allow only patches [OK]

Common Mistakes:

• Assuming ~> 5.0 means < 5.1
• Using ~> 5 without patch version
• Not specifying upper bound explicitly

5. You want to specify a gem version constraint that allows any patch update for version 3.2 but prevents minor version updates to 3.3 or higher. Which constraint should you use?

hard

A. gem 'mygem', '>= 3.2.0', '< 3.3.0'

B. gem 'mygem', '>= 3.2.0'

C. gem 'mygem', '~> 3.2'

D. gem 'mygem', '== 3.2.*'

Solution

1. Step 1: Understand patch vs minor version updates

   Patch updates change the last digit (e.g., 3.2.1), minor updates change the middle digit (e.g., 3.3.0).

2. Step 2: Analyze each constraint

   gem 'mygem', '>= 3.2.0', '< 3.3.0' explicitly allows >= 3.2.0 and < 3.3.0 (3.2.x only). gem 'mygem', '>= 3.2.0' sets only lower bound, allows 3.3+. gem 'mygem', '~> 3.2' allows >= 3.2.0 < 4.0 (allows 3.3). gem 'mygem', '== 3.2.*' uses invalid syntax.

3. Step 3: Select the correct constraint

   The explicit range gem 'mygem', '>= 3.2.0', '< 3.3.0' precisely prevents minor updates beyond 3.2.x.

4. Final Answer:

   gem 'mygem', '>= 3.2.0', '< 3.3.0' -> Option A

5. Quick Check:

   Explicit range prevents minor version updates [OK]

Hint: Use explicit >= and < to lock minor version [OK]

Common Mistakes:

• Using ~> 3.2 which allows minor updates
• Trying invalid wildcard syntax
• Not specifying upper bound to prevent minor updates