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

Rename Compatibility methods to reduce chance of conflicts #515

Merged
merged 1 commit into from
Apr 27, 2014

Conversation

jdelStrother
Copy link
Contributor

Hi - I ran into problems with AATO because I also use FlagShihTzu, which also has a parse_options method mixed into ActiveRecord::Base. I renamed a couple of methods that sounded ambiguously named - WDYT?

In particular, FlagShihTzu also has a parse_options method mixed into ActiveRecord::Base
@seuros
Copy link
Collaborator

seuros commented Apr 21, 2014

This is probably a breaking change ..
cc @bf4

@bf4
Copy link
Collaborator

bf4 commented Apr 27, 2014

I don't think it's a breaking change if it's not part of the public api. I'm ok with the better naming, or a refactor to use an object....

@seuros seuros added this to the 3.2.0 milestone Apr 27, 2014
seuros added a commit that referenced this pull request Apr 27, 2014
Rename Compatibility methods to reduce chance of conflicts
@seuros seuros merged commit 7b21e6a into mbleigh:master Apr 27, 2014
tekniklr pushed a commit to tekniklr/acts-as-taggable-on that referenced this pull request Mar 19, 2021
Rename Compatibility methods to reduce chance of conflicts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants