mass_assign_any_attribute seems broken

[jonathanhall]

'mass_assign_any_attribute true' in the model seems broken.

It allows you to add the properties to a model instance, but 'changed?' is false, so the document does not get saved.

By using 'couchrest_attribute_will_change!' before a save/update call it works as expected

using 1.1.2 and rails 3.0.10 and 3.1.0

[samlown]

Hi, that is very annoying. Looks like we're missing some test coverage. If you feel like adding a test-case that would save us some time and help us get round to it sooner. I suspect the fix would be to disable the changed? check if mass_assign_any_attribute is enabled.

Cheers, sam

[ecuageo]

I ran into this also. Is anyone looking to work on this or should I submit a patch?

[jonathanhall]

I didn't know how to link it up to this on github, but I stuck this up #116
It was a little while ago now, so you might want to confirm it works

[metakeule]

a workaround:

class Person < CouchRest::Model::Base
    mass_assign_any_attribute true
    property :is_updated

    before_validation do
      is_updated_will_change!
    end
end

[pentagon]

is there any pull request to address this issue?