Enum field change

[r00takaspin]

Hello,

I have status field, that has enum type in ActiveRecord. When value of this field changes, old_value is string, but new_value is integer.

Is it bug or feature?

[Marthyn]

bump i got the same problem :/

[Jidek]

bump This problem still exists

[fatkodima]

Which versions of rails and audited are you using? I can't reproduce this issue.

[Jidek]

I was just able to reproduce again. Here are my version numbers: rails (4.2.6), audited (4.2.0).

Steps to reproduce:

1. Have a model with a field defined by an enum, like so:
   
2. Change that field on an audited record

Expected Result:
audited_changes should look like this:

OR like this:

Actual Result:
audited_changes actually looks like this:

I don't think it matters too much if the audited changes shows the keys or the values of the enum, but I would like it to be consistent between old and new.

Please let me know if you have any more questions I can help with for reproducing this issue.

[fatkodima]

@Jidek I have fixed this here #429
Let me know, if this works for you.

[Jidek]

I've been running into a lot of trouble trying to import the fix into my project for testing. It seems bundler won't let me use that branch as other gems have dependencies on the specific version of audited that we use.

Do you have any advice on how to solve the dependency issues? If not I might have to just put together a quick rails demo project for testing the fix.

[fatkodima]

@Jidek In your situation, I think

If not I might have to just put together a quick rails demo project for testing the fix.

is the way to go.

[Jidek]

@fatkodima I finally found some time to set up a demo environment and test your fix. It looks like it's working perfectly.
Thanks for fixing this issue.
Do you have any idea when this might go onto the live version of audited?

[fatkodima]

@Jidek Nice.
No, I have no idea.

[tbrisker]

I haven't had as much time to dedicate to the gem as I wish recently, so progress on the next release has been quite slow. There are several issues I would like to address in the 5.0 release, please see #430 for discussion of those.