Age | Commit message (Collapse) | Author |
---|
| 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://.com/ruby/json/commit/06f00a42e8 |
| https://.com/ruby/json/commit/eed753ffde |
| ruby/ruby#13636 https://.com/ruby/json/commit/6fc2c4b6ab Co-Authored-By: Tim Smith <[email protected]> |
| https://.com/ruby/json/commit/a29cb77d52 |
| https://.com/ruby/json/commit/8603a57a91 |
| https://.com/ruby/json/commit/7c03ffc3e0 |
| https://.com/ruby/json/commit/c060943d04 |
| https://.com/ruby/json/commit/f5c1b8c45d |
| https://.com/ruby/json/commit/8433571dcf |
| https://.com/ruby/json/commit/41f1f6939d Notes: Merged: https://.com/ruby/ruby/pull/13310 |
| https://.com/ruby/json/commit/30e35b9ba5 Notes: Merged: https://.com/ruby/ruby/pull/13310 |
| https://.com/ruby/json/commit/3e025f76d7 |
| https://.com/ruby/json/commit/c985e8c6ea |
| Fix: https://.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://.com/ruby/json/commit/123121bba2 |
| https://.com/ruby/json/commit/84443e881d |
| This time with explicit deprecation warnings. https://.com/ruby/json/commit/0dee9bdad9 |
| https://.com/ruby/json/commit/a6949f8656 |
| https://.com/ruby/json/commit/92beca8032 |
| https://.com/ruby/json/commit/573ebdca89 |
| https://.com/ruby/json/commit/27155b6500 |
| https://.com/ruby/json/commit/3e7e661ef5 |
| https://.com/ruby/json/commit/ff8e18392d |
| By leveraging the `on_load` callback we can move all this logic out of the parser. Which mean we no longer have to duplicate that logic in both parser and that we'll later be able to extract it entirely from the gem. https://.com/ruby/json/commit/f411ddf1ce Notes: Merged: https://.com/ruby/ruby/pull/13004 |
| 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://.com/ruby/json/commit/73d2137fd3 Notes: Merged: https://.com/ruby/ruby/pull/13004 |
| https://.com/ruby/json/commit/eda239ad34 Notes: Merged: https://.com/ruby/ruby/pull/13004 |
| https://.com/ruby/json/commit/1ca7efed1f Notes: Merged: https://.com/ruby/ruby/pull/13004 |
| https://.com/ruby/json/commit/760d922265 Notes: Merged: https://.com/ruby/ruby/pull/13004 |
| https://.com/ruby/json/commit/3de8702354 Notes: Merged: https://.com/ruby/ruby/pull/13004 |
| https://.com/ruby/json/commit/01c47a0555 Notes: Merged: https://.com/ruby/ruby/pull/13004 |
| https://.com/ruby/json/commit/6508455d82 Notes: Merged: https://.com/ruby/ruby/pull/13004 |
| It was only used by JRuby and TruffleRuby to call `SAFE_STATE_.dup` instead of `State.new` which isn't an worthy optimization. Notes: Merged: https://.com/ruby/ruby/pull/12994 |
| https://.com/ruby/json/commit/18e5c3c67c |
| These were deprecated 16 years ago. https://.com/ruby/json/commit/a88d825a91 |
| 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://.com/ruby/json/commit/172762c6e4 |
| https://.com/ruby/json/commit/350c1fd154 |
| https://.com/ruby/json/commit/2e015ff839 |
| https://.com/ruby/json/commit/bea96e0a69 |
| https://.com/ruby/json/commit/aa5b7d6acb |
| https://.com/ruby/json/commit/8b56d47254 |
| Co-authored-by: Jean Boussier <[email protected]> |
| - Also modified the gemspec files' blob as the ragel's `parser.rl` file was removed in https://.com/ruby/json/commit/c8d5236a921e https://.com/ruby/json/commit/b2b106e314 |
| Co-authored-by: Jean Boussier <[email protected]> |
| https://.com/ruby/json/commit/dbcf614e50 |
| https://.com/ruby/json/commit/f8817fe56c Notes: Merged: https://.com/ruby/ruby/pull/12602 |
| https://.com/ruby/json/commit/9e3500f345 Co-authored-by: Jean Boussier <[email protected]> Notes: Merged: https://.com/ruby/ruby/pull/12602 |
| Ref: https://.com/ruby/json/pull/728 Ref: https://.com/ruby/ruby/pull/12569 https://.com/ruby/json/commit/30a4a86954 |
| Ref: https://.com/ruby/json/pull/718 The existing `Parser` interface is pretty bad, as it forces to instantiate a new instance for each document. Instead it's preferable to only take the config and do all the initialization needed, and then keep the parsing state on the stack on in ephemeral memory. This refactor makes the `JSON::Coder` pull request much easier to implement in a performant way. https://.com/ruby/json/commit/c8d5236a92 Co-Authored-By: Étienne Barrié <[email protected]> |
| Co-authored-by: Jean Boussier <[email protected]> Notes: Merged: https://.com/ruby/ruby/pull/12568 |
| https://.com/ruby/json/commit/f745ec145e Notes: Merged: https://.com/ruby/ruby/pull/12394 |
| https://.com/ruby/json/commit/e1f6456499 Notes: Merged: https://.com/ruby/ruby/pull/12267 |