| Age | Commit message (Collapse) | Author |
|
option
https://github.com/ruby/json/commit/a5c160f372
|
|
https://github.com/ruby/json/commit/1cdd2122d5
|
|
https://github.com/ruby/json/commit/e5e4fd558e
|
|
https://github.com/ruby/json/commit/4bdb2d14fe
|
|
https://github.com/ruby/json/commit/ccca602274
|
|
options as second argument
Otherwise it's very error prone.
https://github.com/ruby/json/commit/c54de70f90
|
|
https://github.com/ruby/json/commit/58d60d6b76
|
|
https://github.com/ruby/json/commit/5a12067f88
|
|
This prevent from freezing and sharing state instances.
If you needs some sort of arguments or extra state to the generator
methods, consider using `JSON::Coder` instead.
https://github.com/ruby/json/commit/e9fbc8937f
|
|
https://github.com/ruby/json/commit/826cb2a4f4
|
|
https://github.com/ruby/json/commit/5e61cd7dce
|
|
https://github.com/ruby/json/commit/9e6067bb55
|
|
https://github.com/ruby/json/commit/4abfad090d
|
|
https://github.com/ruby/json/commit/51ce76ea66
|
|
https://github.com/ruby/json/commit/55552cafe2
|
|
https://github.com/ruby/json/commit/3232e8df41
Co-authored-by: Jean Boussier <jean.boussier@gmail.com>
|
|
The gem root was including the test/ directory, so lines from tests were
skipped, and the deprecation warnings were shown as coming from the test
framework.
https://github.com/ruby/json/commit/2ec31a7363
Co-authored-by: Jean Boussier <jean.boussier@gmail.com>
|
|
Fix https://github.com/ruby/json/commit/f411ddf1ceaf
https://github.com/ruby/json/commit/1397bf8cc9
Co-authored-by: Jean Boussier <jean.boussier@gmail.com>
|
|
the correct use of proc argument.
https://github.com/ruby/json/commit/92654cd99b
|
|
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
|
|
Because both strings and symbols keys are serialized the same,
it always has been possible to generate documents with duplicated
keys:
```ruby
>> puts JSON.generate({ foo: 1, "foo" => 2 })
{"foo":1,"foo":2}
```
This is pretty much always a mistake and can cause various
issues because it's not guaranteed how various JSON parsers
will handle this.
Until now I didn't think it was possible to catch such case without
tanking performance, hence why I only made the parser more strict.
But I finally found a way to check for duplicated keys cheaply enough.
|
|
https://github.com/ruby/json/commit/3187c88c06
|
|
https://github.com/ruby/json/commit/19bcfdd8d8
|
|
|
|
https://github.com/ruby/json/commit/72e231f929
|
|
https://github.com/ruby/json/commit/2d2e0d403d
|
|
All the `json/add` related methods for string were
always defined unconditionally from the generators.
It's preferable to only define them if `json/add` is actually used.
|
|
https://github.com/ruby/json/commit/9e3efbfa22
|
|
https://github.com/ruby/json/commit/132049bde2
|
|
Followup: https://github.com/ruby/json/pull/818
Now the warning should point at the `JSON.parse` caller, and not
inside the json gem itself.
https://github.com/ruby/json/commit/cd51557387
|
|
https://github.com/ruby/json/commit/cfe9337eda
|
|
https://github.com/ruby/json/commit/8d08494dee
|
|
There are few legitimate use cases for duplicate keys, and can
in some case be exploited.
Rather to always silently accept them, we should emit a warning,
and in the future require to explictly allow them.
https://github.com/ruby/json/commit/06f00a42e8
|
|
https://github.com/ruby/json/commit/eed753ffde
|
|
ruby/ruby#13636
https://github.com/ruby/json/commit/6fc2c4b6ab
Co-Authored-By: Tim Smith <tsmith84@gmail.com>
|
|
https://github.com/ruby/json/commit/a29cb77d52
|
|
https://github.com/ruby/json/commit/8603a57a91
|
|
https://github.com/ruby/json/commit/7c03ffc3e0
|
|
https://github.com/ruby/json/commit/c060943d04
|
|
https://github.com/ruby/json/commit/f5c1b8c45d
|
|
https://github.com/ruby/json/commit/8433571dcf
|
|
https://github.com/ruby/json/commit/41f1f6939d
Notes:
Merged: https://github.com/ruby/ruby/pull/13310
|
|
https://github.com/ruby/json/commit/30e35b9ba5
Notes:
Merged: https://github.com/ruby/ruby/pull/13310
|
|
https://github.com/ruby/json/commit/3e025f76d7
|
|
https://github.com/ruby/json/commit/c985e8c6ea
|
|
Fix: https://github.com/ruby/json/issues/788
`multi_json` rely on it, even though it was never documented as
public API.
Bringing it back as a method so it can emit a deprecation warning.
https://github.com/ruby/json/commit/123121bba2
|
|
https://github.com/ruby/json/commit/84443e881d
|
|
This time with explicit deprecation warnings.
https://github.com/ruby/json/commit/0dee9bdad9
|
|
https://github.com/ruby/json/commit/a6949f8656
|
|
https://github.com/ruby/json/commit/92beca8032
|