Skip to content
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

JSON load/dump issue on Rails 3.1 #42

Open
thhermansen opened this issue Jun 5, 2011 · 1 comment
Open

JSON load/dump issue on Rails 3.1 #42

thhermansen opened this issue Jun 5, 2011 · 1 comment
Milestone

Comments

@thhermansen
Copy link
Contributor

We have a small issue with MassiveRecord and Rails 3.1 (well, ActiveSupport::JSON that is). In the 3.0 series the JSON decoder used a YAML backend as default. Meaning that we could ask it to decode "1" and it would return the Fixnum 1. This no longer works as ActiveSupport::JSON now by default uses the JSON gem. It seems to be a bit stricter, and will not decode the "1" into a Fixnum.

So, we'll need to change our load/dump strategy a bit and make it a bit smarter not running simple types like fixnum via the coder.

@thhermansen
Copy link
Contributor Author

Maybe #80 can help this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant