Closed byroot closed 3 weeks ago
Followup: https://github.com/ruby/json/pull/633
That's what was raised historically. You could argue that this new exception is more precise, but I've encountered some real production code that expected the old behavior and that was broken by this change.
Followup: https://github.com/ruby/json/pull/633
That's what was raised historically. You could argue that this new exception is more precise, but I've encountered some real production code that expected the old behavior and that was broken by this change.