CODEWITHSUNDEEP
ruby-on-railsrubyrubocopcode-climateruby-2.3
John Smith
John Smith

Reputation: 6259

fix `Missing frozen string literal comment` issue

I created a new migration, it looks like this one:

class AddCommentsToUsers < ActiveRecord::Migration
  def change
    add_column :users, :comments, :text
  end
end

Now with Code Climate I am warned of an issue: Missing frozen string literal comment.

I tried to fix it like this:

# frozen_string_literal: true
class AddCommentsToUsers < ActiveRecord::Migration
  def change
    add_column :users, :comments, :text
  end
end

But I still have the same issue. How can I solve it? Thanks.

Upvotes: 21

Views: 26824

Answers (4)

VENKATESH KARNI
VENKATESH KARNI

Reputation: 66

Run bundle exec rubocop --parallel -A (AUTO FIX)

AND

RUN AGAIN bundle exec rubocop --parallel OR rubocop

Try....

Upvotes: 0

Van_Paitin
Van_Paitin

Reputation: 4248

I experienced the same problem. Rubocop was working fine before but suddenly it started acting up. I read through their configuration options on github and saw the particular property that is messing with your code. The property can be found here: FrozenStringLiteral.

To silence this warning, you only need to add this to your rubocop.yml file

Style/FrozenStringLiteralComment:
  Enabled: false

Upvotes: 15

debao84
debao84

Reputation: 103

Adding an empty line below the string literal line fixed it for me.

# frozen_string_literal: true

module FooBar
end

Upvotes: 4

user18802398
user18802398

Reputation: 1

Make sure you added your changes to the staging area before trying to run Rubocop again. I had the same problem and that solved it for me.

Upvotes: 0

Related Questions