ruby.git/test/json/json_common_interface_test.rb, branch v4.0.4

[ruby/json] Fix duplicated test_unsafe_load_with_options test case

2025-12-03T14:13:39+00:00

https://github.com/ruby/json/commit/7b62fac525

[ruby/json] Improve `JSON.load` and `JSON.unsafe_load` to allow passing options as second argument

2025-12-03T13:48:31+00:00

Otherwise it's very error prone.

https://github.com/ruby/json/commit/c54de70f90

[ruby/json] Get rid of JSON.deep_const_get (private API)

2025-11-07T08:46:00+00:00

https://github.com/ruby/json/commit/826cb2a4f4

Use Time.new because JSON.unsafe_load losts fractions of a second and

2025-09-03T14:38:37+00:00

JSON.unsafe_load with Time object returns String

```
  1) Failure:
JSONCommonInterfaceTest#test_unsafe_load_default_options [/path/to/ruby/test/json/json_common_interface_test.rb:230]:
<2025-09-03 14:28:31.293635 +0200> expected but was
<"2025-09-03 14:28:31 +0200">.
```

[ruby/json] Added testing for JSON.unsafe_load. Fixes NoMethodError

2025-09-03T14:38:37+00:00

when passing proc to JSON.unsafe_load, matching the changes made in
https://github.com/ruby/json/commit/73d2137fd3ad.

https://github.com/ruby/json/commit/77292cbc9b

[ruby/json] Stop caching the generator state pointer

2025-04-30T06:12:41+00:00

Fix: https://github.com/ruby/json/issues/790

If we end up calling something that spills the state
on the heap, the pointer we received is outdated and
may be out of sync.

https://github.com/ruby/json/commit/2ffa4ea46b

[ruby/json] Add missing assert_deprecated_warning

2025-03-28T03:44:53+00:00

https://github.com/ruby/json/commit/1b16a82980

[ruby/json] JSON.load invoke the proc callback directly from the parser.

2025-03-28T03:44:53+00:00

And substitute the return value like `Marshal.load` doesm
which I can only assume was the intent.

This also open the door to re-implement all the `create_addition`
logic in `json/common.rb`.

https://github.com/ruby/json/commit/73d2137fd3

[ruby/json] Deprecate all `*_default_options`

2025-03-27T02:37:27+00:00

Globally changing the behavior of the library is a bad idea, as
many different libraries may rely on `json` and may not expect it
and likely never tested that a different default config works for them.

If you need to change the behavior of JSON, it's best to do it only
locally, and not globally.

In addition the new `JSON::Coder` interface is much more suited for
that.

Another reason for the deprecation is that it's impossible to
make `JSON.load` and `JSON.dump` Ractor-safe with such API.

https://github.com/ruby/json/commit/172762c6e4

[ruby/json] JSON.dump: write directly into the provided IO

2024-11-26T06:11:05+00:00

Ref: https://github.com/ruby/json/issues/524

Rather than to buffer everything in memory.

Unfortunately Ruby doesn't provide an API to write into
and IO without first allocating a string, which is a bit
wasteful.

https://github.com/ruby/json/commit/f017af6c0a