Load source proc nil options object.
Ruby json load symbolize names.
One main difference is on json parse the standard json gem takes a symbolize names option while yajl takes symbolize keys.
A source can either be a string like object an io like object or an object responding to the read method.
Load a ruby data structure from a json source and return it.
There already is a ticket on the yajl ruby gem to make it play nice with the json gem.
To modify the default options pass in the optional options argument as well.
If proc was given it will be called with any nested ruby object as an argument recursively in depth first order.
Run irb sonsole require json json parse nil quirks mode true got segfault.
When trying to symbolize keys on json parsing it s really hard to remember the name symbolize names.
Json load file new names json reads the json inside the file and results in a ruby object.
Some name works just like parse in fact it converts any object that responds to a read method.
Brianmario yajl ruby 94 luckily both params can be passed to either gem and have it function as desired.
If proc was given it will be called with any nested ruby object as an argument recursively in depth first order.
To modify the default options pass in the optional options argument as well.
Json load takes either a string or io file etc and converts that to ruby hash array.
Load a ruby data structure from a json source and return it.
To modify the default options pass in the optional options argument as well.
True i would like to propose that we change this keyword to symbolize keys to be more clear.
If proc was given it will be called with any nested ruby object as an argument recursively in depth first order.