A source can either be a string like object an io like object or an object responding to the read method.
Ruby json load symbolize names.
If proc was given it will be called with any nested ruby object as an argument recursively in depth first order.
A source can either be a string like object an io like object or an object responding to the read method.
If proc was given it will be called with any nested ruby object as an argument recursively in depth first order.
Json load takes either a string or io file etc and converts that to ruby hash array.
To modify the default options pass in the optional options argument as well.
Load a ruby data structure from a json source and return it.
True i would like to propose that we change this keyword to symbolize keys to be more clear.
One main difference is on json parse the standard json gem takes a symbolize names option while yajl takes symbolize keys.
Load a ruby data structure from a json source and return it.
When trying to symbolize keys on json parsing it s really hard to remember the name symbolize names.
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.
A source can either be a string like object an io like object or an object responding to the read method.
To modify the default options pass in the optional options argument as well.
Load a ruby data structure from a json source and return it.
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.
Load source proc nil options object.
There already is a ticket on the yajl ruby gem to make it play nice with the json gem.