-
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
Dirty checking not working for context tags #321
Comments
👍 Confirmed, causing issue when using tag list fields in nested forms. |
class User < ActiveRecord::Base
acts_as_taggable_on :admin_tags
end
So it looks like the fundamental assumption of dirty.rb is flawed: def #{tag_type}_list_changed?
changed_attributes.include?("#{tag_type}_list")
end Using Rails 3.2.13 on Ruby 1.9.3-p392 |
Thanks for the failing specs. Is a fix underway or should I take a look? |
I'm taking a look, but I don't know the library to well. If you've got a lead, let me know and I'll try it out. |
I'm not available right now, but might be in a few hours. I've marked this one to be included in 2.5.0, since I am even having trouble releasing 2.4.0 at this time. So try to be patient, there is a backlog with issues. |
Related mbleigh#321. Split tests for single-assertions
2.4.0 will be out on Tuesday and I think 2.5.0 (which will include your fix) should come fairly close behind. Thanks for the contribution! |
Just to be clear, your fix will be in 2.4.1 already. |
This reverts commit e44b69d. This undid the work of 16c4567 such that we were now re-including most the library on subsequent calls of the macro method like: acts_as_taggable_on :pros acts_as_taggable_on :cons The change was made in order to fix dirty tracking on mbleigh#321, but the proper fix is that the dirty tracking module is missing a hook `acts_as_taggable_on` macro that calls super.
This reverts commit e44b69d. This undid the work of 16c4567 such that we were now re-including most the library on subsequent calls of the macro method like: acts_as_taggable_on :pros acts_as_taggable_on :cons The change was made in order to fix dirty tracking on mbleigh#321, but the proper fix is that the dirty tracking module is missing a hook `acts_as_taggable_on` macro that calls super.
Related mbleigh#321. Split tests for single-assertions
Fix dirty checking for subsequent calls to taggable_on. Fixes mbleigh#321.
Can someone please confirm this bug:
The text was updated successfully, but these errors were encountered: