ruby.git/test/json/json_coder_test.rb, branch v4.0.2

[ruby/json] Respect Coder depth when generating

2025-11-27T13:01:57+00:00

https://github.com/ruby/json/commit/9c36681b17

[ruby/json] Test current behavior regarding depth for Coder

2025-11-27T13:01:56+00:00

Coder currently ignores its depth and always resets it to 0 when
generating a new JSON document.

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

[ruby/json] Invoke `as_json` callback for strings with invalid encoding

2025-11-02T14:48:33+00:00

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

This allow users to encode binary strings if they so wish.
e.g. they can use Base64 or similar, or chose to replace invalid
characters with something else.

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

[ruby/json] Fix concurrent usage of JSON::Coder#dump

2025-10-25T08:57:48+00:00

Fix: https://github.com/rails/rails/commit/90616277e3d8fc46c9cf35d6a7470ff1ea0092f7#r168784389

Because the `depth` counter is inside `JSON::State` it can't be used
concurrently, and in case of a circular reference the counter may be
left at the max value.

The depth counter should be moved outside `JSON_Generator_State` and
into `struct generate_json_data`, but it's a larger refactor.

In the meantime, `JSON::Coder` calls `State#generate_new` so I changed
that method so that it first copy the state on the stack.

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

`JSON::Coder` callback now recieve a second argument to mark object keys

2025-09-19T10:30:10+00:00

e.g.
```ruby
{ 1 => 2 }
```

The callback will be invoked for `1` as while it has a native JSON
equivalent, it's not legal as an object name.

Fix `JSON::Coder` to cast non-string keys.

2025-08-27T01:01:52+00:00

Fix JSON::Coder to call as_json proc for NaN and Infinity

2025-02-06T07:02:03+00:00

Co-authored-by: Jean Boussier

Introduce JSON::Coder

2025-01-28T06:41:47+00:00

Co-authored-by: Jean Boussier