should_belong_to generates DEPRECATION WARNING (Rails 3.1)

[ultrasaurus]

should_belong_to :whatever
in a spec for a Rails 3.1 app, causes this warning:

DEPRECATION WARNING: primary_key_name is deprecated and will be removed from Rails 3.2 (use foreign_key instead). (called from reflection_foreign_key at .../gems/remarkable_activerecord-4.0.0.alpha4/lib/remarkable/active_record/matchers/association_matcher.rb:97)

Thanks!

[structuralartistry]

Hi, if you use: gem 'shoulda', '>= 3.0.0.beta', the deprecation error goes away.

[saks]

+1 for this problem. It's really hard to read rspec output.

[papricek]

+1

[plribeiro3000]

This bug was already fixed and is on master. You still have the problem because the gem wasnt been regenerated since version 4.0.0.alpha4. Try to download the version from this repo and use it instead of the one from rubygems.

[jcf]

Remarkable does not work with Rails 3.2 because of this issue. Can we get a release of the change to reflection_foreign_key please?

[mkuklis]

+1

[dzaporozhets]

+1

[sbackus]

+1