-
Notifications
You must be signed in to change notification settings - Fork 333
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.dump: handle unenclosed hashes regression #554
Conversation
Fix: ruby#553 We can never add keyword arguments to `dump` otherwise existing code using unenclosed hash will break.
👍 |
@byroot Now |
No it's not... but since it's a new feature it's less if a problem. I'll submit another PR soon. Thank you for letting me know |
Locks the json gem to 2.6.3 until there is a new release that includes ruby/json#554
If I may: #556 |
private | ||
|
||
def merge_dump_options(opts, strict: NOT_SET) | ||
opts[:strict] = strict if NOT_SET != strict |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can destructively modify JSON.dump_default_options
. I addressed that in #556.
Locks the json gem to 2.6.3 until there is a new release that includes ruby/json#554
Don't use `json` 2.7.0 release that has a regression. Ref: ruby/json#554
Fix: #553
We can never add keyword arguments to
dump
otherwise existing code using unenclosed hash will break.cc @hsbt