-
Notifications
You must be signed in to change notification settings - Fork 21.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
try doesn't work properly in rails 3.1.1 #3264
Comments
This was actually a bug in Rails 3.1.0. |
The right code: Name.no_slug if Name.respond_to?(:no_slug) |
to be frankly , i really love the try "feature" before.. :-) |
@29decibel yes, it was convenient also! Different method though. |
@jeremy why isn't the change documented in the ChangeLog: http://weblog.rubyonrails.org/2011/10/7/ann-rails-3-1-1 ? |
@BetelGuese it might have been missed. The post contains a GitHub link for the exhaustive list of changes :) |
@vijaydev Considering that this can make previously running code start throwing an exception I would deem it important enough to be part of the ChangeLog. Can it be added still? |
In my application I have logic that calls try on model. Like Name.try(:no_slug). It worked in rails 3.1.0, but in rails 3.1.1 I get exception.
The text was updated successfully, but these errors were encountered: