thoughtbot/paperclip

View on GitHub
Gemfile

Summary

Maintainability
Test Coverage

Prefer double-quoted strings unless you need single quotes to avoid extra backslashes for escaping.
Open

gem 'pry'
Severity: Minor
Found in Gemfile by rubocop

Prefer double-quoted strings unless you need single quotes to avoid extra backslashes for escaping.
Open

gem 'sqlite3', '~> 1.3.8', :platforms => :ruby
Severity: Minor
Found in Gemfile by rubocop

Prefer double-quoted strings unless you need single quotes to avoid extra backslashes for escaping.
Open

  gem 'rubocop', require: false
Severity: Minor
Found in Gemfile by rubocop

Prefer double-quoted strings unless you need single quotes to avoid extra backslashes for escaping.
Open

  gem 'activerecord-import'
Severity: Minor
Found in Gemfile by rubocop

Prefer double-quoted strings unless you need single quotes to avoid extra backslashes for escaping.
Open

gem 'sqlite3', '~> 1.3.8', :platforms => :ruby
Severity: Minor
Found in Gemfile by rubocop

Gem pry should appear before sqlite3 in their gem group.
Open

gem 'pry'
Severity: Minor
Found in Gemfile by rubocop

Gems in consecutive lines should be alphabetically sorted

Example:

# bad
gem 'rubocop'
gem 'rspec'

# good
gem 'rspec'
gem 'rubocop'

# good
gem 'rubocop'

gem 'rspec'

Prefer double-quoted strings unless you need single quotes to avoid extra backslashes for escaping.
Open

  gem 'mime-types'
Severity: Minor
Found in Gemfile by rubocop

Use the new Ruby 1.9 hash syntax.
Open

gem 'sqlite3', '~> 1.3.8', :platforms => :ruby
Severity: Minor
Found in Gemfile by rubocop

This cop checks hash literal syntax.

It can enforce either the use of the class hash rocket syntax or the use of the newer Ruby 1.9 syntax (when applicable).

A separate offense is registered for each problematic pair.

The supported styles are:

  • ruby19 - forces use of the 1.9 syntax (e.g. {a: 1}) when hashes have all symbols for keys
  • hash_rockets - forces use of hash rockets for all hashes
  • nomixedkeys - simply checks for hashes with mixed syntaxes
  • ruby19nomixed_keys - forces use of ruby 1.9 syntax and forbids mixed syntax hashes

Example:

"EnforcedStyle => 'ruby19'"

# good
{a: 2, b: 1}
{:c => 2, 'd' => 2} # acceptable since 'd' isn't a symbol
{d: 1, 'e' => 2} # technically not forbidden

# bad
{:a => 2}
{b: 1, :c => 2}

Example:

"EnforcedStyle => 'hash_rockets'"

# good
{:a => 1, :b => 2}

# bad
{a: 1, b: 2}
{c: 1, 'd' => 5}

Example:

"EnforcedStyle => 'no_mixed_keys'"

# good
{:a => 1, :b => 2}
{c: 1, d: 2}

# bad
{:a => 1, b: 2}
{c: 1, 'd' => 2}

Example:

"EnforcedStyle => 'ruby19_no_mixed_keys'"

# good
{a: 1, b: 2}
{:c => 3, 'd' => 4}

# bad
{:a => 1, :b => 2}
{c: 2, 'd' => 3} # should just use hash rockets

Prefer double-quoted strings unless you need single quotes to avoid extra backslashes for escaping.
Open

  gem 'builder'
Severity: Minor
Found in Gemfile by rubocop

Gem builder should appear before mime-types in their gem group.
Open

  gem 'builder'
Severity: Minor
Found in Gemfile by rubocop

Gems in consecutive lines should be alphabetically sorted

Example:

# bad
gem 'rubocop'
gem 'rspec'

# good
gem 'rspec'
gem 'rubocop'

# good
gem 'rubocop'

gem 'rspec'

There are no issues that match your filters.

Category
Status