Skip to content
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

Fix Rails 3.2 compatibility by not using try #72

Merged
merged 1 commit into from
May 21, 2016

Conversation

mattbrictson
Copy link
Collaborator

The ActiveSupport try method works differently in different versions of Rails. In some versions it checks respond_to?; others do not. It is safer (and more compatible) to explicitly use respond_to? instead.

Fixes #71

@mattbrictson
Copy link
Collaborator Author

@nnc Can you test my branch and verify it fixes the Rails 3.2 problem you're having? Thanks!

@mattbrictson mattbrictson added this to the 0.1.21 milestone May 20, 2016
The ActiveSupport `try` method works differently in different versions of Rails.
In some versions it checks `respond_to?`; others do not. It is safer (and more
compatible) to explicitly use `respond_to?` instead.
@nnc
Copy link

nnc commented May 21, 2016

@mattbrictson works like a charm. Thanks!

@mattbrictson mattbrictson merged commit b67d8b3 into brentd:master May 21, 2016
@mattbrictson mattbrictson deleted the fix-rails-32 branch July 3, 2023 15:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants