-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Fixed bug with Rails 4 and association#to_sql #367
Conversation
The tests in Travis are passing, so it looks good. But yes please provide tests for this, as I want to make sure it remains fixed in the future. |
are the appraisal tests for rails-4 passing for you? working on those tests. |
two things. mostly separate.
|
Travis says it's good to merge: https://travis-ci.org/mbleigh/acts-as-taggable-on/builds/7885639 Unfortunately I have literally packed my bags to go on holidays. Will be back June 28 and can only take a proper look then I'm afraid. |
all good. let's pick this back up then. i'm never sure what to do on tests for commits like this. thanks. |
👍 |
Any progress on this? |
Fixed bug with Rails 4 and association#to_sql
Thanks, looks good. These kinds of issues are probably solved using ARel throughout as well. |
Thanks @tilsammans! |
Fixed bug with Rails 4 and association#to_sql
You can see the issue here: https://coderwall.com/p/45ombq [as well as how I fixed it]. This problem raises itself in acts-as-taggable-on when you try something like:
I didn't include tests because when I ran the suite via rake appraisal:rails-4 there was a lot of errors and I wasn't sure whether committing to a red suite was any better. If you guys want, I totally can write tests for this.