We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using the gem by itself, everything seems fine:
$ irb irb(main):001:0> require 'syck' => true irb(main):002:0> Syck::VERSION => "1.0.5" irb(main):003:0> Syck.dump({'a'=>1,'b'=>2}) => "--- \na: 1\nb: 2\n" irb(main):004:0> {'a'=>1,'b'=>2}.to_yaml => "--- \na: 1\nb: 2\n"
Yet somehow, when running alongside Rails, it serialises nothing other than the hash itself:
$ script/rails console Loading development environment (Rails 3.2.22.2) irb(main):001:0> Syck::VERSION => "1.0.5" irb(main):002:0> Syck.dump({'a'=>1,'b'=>2}) => "--- {}\n\n" irb(main):003:0> {'a'=>1,'b'=>2}.to_yaml => "--- {}\n\n"
These are both using syck 1.1.0, but the version is reported as 1.0.5 for some reason.
Running actual 1.0.5, everything works fine again, so I guess this is a regression in 1.1.0.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When using the gem by itself, everything seems fine:
Yet somehow, when running alongside Rails, it serialises nothing other than the hash itself:
These are both using syck 1.1.0, but the version is reported as 1.0.5 for some reason.
Running actual 1.0.5, everything works fine again, so I guess this is a regression in 1.1.0.
The text was updated successfully, but these errors were encountered: