diff options
| author | Florian Frank <flori@ping.de> | 2016-06-02 14:13:37 +0200 |
|---|---|---|
| committer | Florian Frank <flori@ping.de> | 2016-06-02 14:13:37 +0200 |
| commit | a985a0c4b074280e2a9e215ead95b1e66797b6c3 (patch) | |
| tree | 6924ec2cf10395a2d9f03bac15bd7d44923417d5 | |
| parent | 08b6febac4f2382f2526c51060b630b7b7130577 (diff) | |
| download | json-a985a0c4b074280e2a9e215ead95b1e66797b6c3.tar.gz | |
Update documentation for RFC 7159 support
| -rw-r--r-- | README.md | 11 |
1 files changed, 0 insertions, 11 deletions
@@ -25,13 +25,6 @@ encoded, please use the to\_json\_raw\_object method of String (which produces an object, that contains a byte array) and decode the result on the receiving endpoint. -The JSON parsers can parse UTF-8, UTF-16BE, UTF-16LE, UTF-32BE, and UTF-32LE -JSON documents under Ruby 1.8. Under Ruby 1.9 they take advantage of Ruby's -M17n features and can parse all documents which have the correct -String#encoding set. If a document string has ASCII-8BIT as an encoding the -parser attempts to figure out which of the UTF encodings from above it is and -trys to parse it. - ## Installation It's recommended to use the extension variant of JSON, because it's faster than @@ -91,10 +84,6 @@ You can also use the pretty\_generate method (which formats the output more verbosely and nicely) or fast\_generate (which doesn't do any of the security checks generate performs, e. g. nesting deepness checks). -To create a valid JSON document you have to make sure, that the output is -embedded in either a JSON array [] or a JSON object {}. The easiest way to do -this, is by putting your values in a Ruby Array or Hash instance. - There are also the JSON and JSON[] methods which use parse on a String or generate a JSON document from an array or hash: |