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
[Informative] deep_symbolize_keys
broken in Rails 7 with Mash
#559
Comments
We should probably @DerekYu177 It would be awesome if you could turn this into a failing spec w/Rails 7 in hashie. |
Opened. |
This appears to be issue in Rails 7 when using |
@aflansburg Do you think you could contribute an integration spec for Rails 7 similar to https://github.com/hashie/hashie/tree/master/spec/integration/rails? (maybe that should be called rails6) |
@dblock can do - for what it's worth I was able to get around this by doing
|
deep_symbolize_keys
will no longer work in Rails 7 with Mash
deep_symbolize_keys
broken in Rails 7 with Mash
Pending spec merged in #569, maybe someone wants to try and fix the issue? |
Related tangentially to #514
In Rails ~> 6 versions, calling
deep_symbolize_keys
would instantiate a newHash
class when transforming keys in objects.However, in Rails 7+, this has changed to instead be a
self.class.new
which would be a newHashie::Mash
. Digging into the accesses, it looks like by default internal keys are converted to strings, which renders the output of#deep_symbolize_keys
unchanged.I think this might be too small of an case to document to the readme, but I leave this as a known implementation bug to the authors.
The text was updated successfully, but these errors were encountered: