Rubocop for linting in Ruby - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to run Rubocop on a Ruby file named example.rb.

Ruby

rubocop [1]

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

Aexample.rb

B--fix

C--version

D--help

Attempts:

3 left

💡 Hint

Common Mistakes

Using options like --fix or --version instead of the file name.

Not specifying any file to check.

To check a Ruby file with Rubocop, you run rubocop example.rb.

2fill in blank

medium

Complete the command to automatically fix offenses in script.rb using Rubocop.

Ruby

rubocop [1] script.rb

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

A--fix

B--auto-correct

C--version

D--help

Attempts:

3 left

💡 Hint

Common Mistakes

Using --fix which is not a valid Rubocop option.

Using --version or --help which do not fix code.

The --auto-correct option tells Rubocop to fix offenses automatically.

3fill in blank

hard

Fix the error in the Rubocop command to check all Ruby files in the current directory.

Ruby

rubocop [1]

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

A*.rb

B*.py

Call.rb

Drubyfiles

Attempts:

3 left

💡 Hint

Common Mistakes

Using file extensions for other languages like .py.

Using incorrect file names or folder names.

Using *.rb tells Rubocop to check all Ruby files in the current folder.

4fill in blank

hard

Fill both blanks to create a Rubocop configuration file that disables the Style/StringLiterals cop.

Ruby

Style/StringLiterals:
  Enabled: [1]
  EnforcedStyle: [2]

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

Afalse

Btrue

Cdouble_quotes

Dsingle_quotes

Attempts:

3 left

💡 Hint

Common Mistakes

Setting Enabled to true when wanting to disable.

Confusing quote styles.

Setting Enabled: false disables the cop. EnforcedStyle: single_quotes sets preferred quotes style.

5fill in blank

hard

Fill all three blanks to write a Rubocop command that checks app.rb, shows only offenses with severity 'error', and uses color output.

Ruby

rubocop [1] app.rb --severity [2] --[3]

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

A--only

Berror

Ccolor

D--auto-correct

Attempts:

3 left

💡 Hint

Common Mistakes

Using --auto-correct instead of --color for colored output.

Not specifying severity correctly.

The --only option limits checks, error filters severity, and --color enables colored output.

Practice

1.

What is the main purpose of using Rubocop in Ruby programming?

easy

A. To manage Ruby gem dependencies

B. To run Ruby programs faster

C. To check code style and find errors

D. To compile Ruby code into machine code

Solution

1. Step 1: Understand Rubocop's role

   Rubocop is a tool that checks Ruby code for style issues and errors.

2. Step 2: Compare options

   Only To check code style and find errors describes checking code style and errors, which matches Rubocop's purpose.

3. Final Answer:

   To check code style and find errors -> Option C

4. Quick Check:

   Rubocop = code style and error checker [OK]

Hint: Rubocop checks style and errors, not speed or compilation [OK]

Common Mistakes:

• Thinking Rubocop runs or compiles code
• Confusing Rubocop with dependency managers
• Assuming Rubocop improves runtime speed

2.

Which command correctly runs Rubocop on your Ruby project from the terminal?

easy

A. execute rubocop

B. ruby rubocop

C. run rubocop

D. rubocop

Solution

1. Step 1: Identify the correct command

   The standard command to run Rubocop is simply rubocop in the terminal.

2. Step 2: Eliminate incorrect options

   Options B, C, and D are not valid terminal commands for Rubocop.

3. Final Answer:

   rubocop -> Option D

4. Quick Check:

   Run Rubocop with 'rubocop' command [OK]

Hint: Just type 'rubocop' in terminal to run it [OK]

Common Mistakes:

• Adding 'ruby' before rubocop
• Using 'run' or 'execute' commands incorrectly
• Confusing Rubocop command with Ruby interpreter

3.

Given this Ruby code saved in example.rb:

def greet(name)
  puts "Hello, #{name}!"
end

greet("Alice")

You run rubocop example.rb and get a warning about missing a blank line after method definition. What will Rubocop suggest?

medium

A. Add a blank line after the end of the method

B. Remove the blank line before calling greet

C. Change puts to print

D. Rename the method to greeting

Solution

1. Step 1: Understand Rubocop's style rule

   Rubocop often requires a blank line after method definitions for readability.

2. Step 2: Identify the suggested fix

   The warning suggests adding a blank line after the end of greet method, before the next code.

3. Final Answer:

   Add a blank line after the end of the method -> Option A

4. Quick Check:

   Blank line after method end = Rubocop style [OK]

Hint: Rubocop likes blank lines after method ends [OK]

Common Mistakes:

• Ignoring blank line warnings
• Changing code logic instead of style
• Misunderstanding the warning message

4.

Look at this Ruby code snippet:

def add(a, b)
  a + b
end

puts add(2, 3)

When running rubocop, you get an error about missing parentheses in method call. How do you fix it?

medium

A. Remove parentheses from def add(a, b)

B. Add parentheses around arguments in puts add(2, 3)

C. Add parentheses around a + b inside method

D. Change method name to add_numbers

Solution

1. Step 1: Understand Rubocop's style on method calls

   Rubocop prefers explicit parentheses in method calls with arguments for clarity.

2. Step 2: Apply fix to method call

   The call puts add(2, 3) should have parentheses around add(2, 3) to avoid ambiguity.

3. Final Answer:

   Add parentheses around arguments in puts add(2, 3) -> Option B

4. Quick Check:

   Method calls with args need parentheses [OK]

Hint: Put parentheses around method call arguments [OK]

Common Mistakes:

• Removing parentheses from method definitions
• Adding parentheses inside expressions unnecessarily
• Ignoring Rubocop's parentheses style

5.

You want to configure Rubocop to ignore style warnings about line length in your project. Which file and setting should you modify?

hard

A. Add Metrics/LineLength: with Enabled: false in .rubocop.yml

B. Add LineLength: ignore in Gemfile

C. Set rubocop --ignore-line-length in terminal

D. Remove rubocop gem from Gemfile

Solution

1. Step 1: Identify Rubocop config file

   Rubocop uses .rubocop.yml file to configure rules.

2. Step 2: Disable line length check

   Inside .rubocop.yml, setting Metrics/LineLength: Enabled: false disables that check.

3. Final Answer:

   Add Metrics/LineLength: with Enabled: false in .rubocop.yml -> Option A

4. Quick Check:

   Disable rules in .rubocop.yml [OK]

Hint: Disable rules in .rubocop.yml config file [OK]

Common Mistakes:

• Trying to disable rules via Gemfile
• Using wrong command line flags
• Removing Rubocop gem instead of configuring