"Nothing to annotate" in rails 4.2

[ekampp]

Disclaimer: I'm aware that 4.2 is in alpha at the moment.

After upgrading to rails 4.2.0.alpha, annotation always yields Nothing annotated.

Running it with the bundle exec annotate --trace parameter yields the following:

State :complete for :levelup_state is already defined in :state
/Users/emil/.rbenv/versions/2.1.0/lib/ruby/gems/2.1.0/gems/closure_tree-4.4.0/lib/closure_tree/support.rb:29: warning: already initialized constant FeatHierarchy
/Users/emil/.rbenv/versions/2.1.0/lib/ruby/gems/2.1.0/gems/closure_tree-4.4.0/lib/closure_tree/support.rb:29: warning: previous definition of FeatHierarchy was here
Nothing annotated.

As you can see, the warnings are unrelated to Annotate, and yields nothing of interest indicating why the annotation didn't find any models to annotate, even though there's several models in the project.

[ctran]

The latest version is actually 2.6.2. You may wan to try that.

[ekampp]

I have both tried the latest gem >= 2.6.2 and directly from github. Neither solves the problem. And it seems to work when using rails 4.0 and 4.2 4.1.

[seuros]

@ekampp
And it seems to work when using rails 4.0 and 4.2. you mean 4.1

[ekampp]

Indeed I do, @seuros, thanks.

[rahuljayaraman]

Facing the same issues with v2.6.3 & edge rails (4.2.0.alpha)

[ctran]

Sorry, 2.6.3 just has a small fix.

[bigardone]

Same issue here using 2.6.3 and Rails 4.1.1

[ekampp]

I found the offending line: lib/annotate/annotate_models.rb:386, which tries (e.g.) 'User' == 'user', which is never true.
So it seems the problem is in the ActiveSupport::Inflector.underscore method, which may once have underscores a class, but doesn't any more. Now it seems it can only handle strings.

[dlynam]

I'm seeing this issue in Rails 4.2.0 (Ruby 2.2.0) still. I've tried multiple versions (v2.6.6 and v2.6.7). Could this still be an issue?

[ekampp]

@dlynam are you sure it's the exact same issue? I haven't used this gem for a while, so I don't know if this is still an issue. Can you track down, where your exact problem arises from?

[dlynam]

@ekampp looks like this issue has already been fixed, just not pushed to -v2.6.7 #235

[bcackerman]

Running gem 'annotate', '2.6.5' and it works. I rolled back from 2.7.1