Changing collection breaks history tracking about mongoid-history HOT 5 CLOSED

And if you move store_in above that track_history does it change anything? Either way I think it's a bug and the scope should include the target collection. Try PRing a full spec and maybe a fix, I can try helping with that too.

from mongoid-history.

@dblock yes, that fixes it. I can PR a fix that substitutes class name as the key instead of collection, but the tests wont pass. The other solution I was thinking is to store the options on the class itself but I think that messes with inheritance.

The end goal is to have a set-and-forget module that can be included anywhere, and ideally everywhere to track every change.

from mongoid-history.

I think storing options on the class itself is the way to go, and it can use class level attributes that are copied on inheritance but become local to the child class when modified. I am not saying it's easy, but you'll be my hero if you can make it work :)

from mongoid-history.

It's going to break some tests. I'll code it up and report back.

from mongoid-history.

Closed via #227

from mongoid-history.