| … | |
… | |
| 347 | future, global hooks might get installed that influence C<decode> and are |
347 | future, global hooks might get installed that influence C<decode> and are |
| 348 | enabled by this setting. |
348 | enabled by this setting. |
| 349 | |
349 | |
| 350 | If C<$enable> is false, then the C<allow_blessed> setting will decide what |
350 | If C<$enable> is false, then the C<allow_blessed> setting will decide what |
| 351 | to do when a blessed object is found. |
351 | to do when a blessed object is found. |
|
|
352 | |
|
|
353 | =item $json = $json->filter_json_object ([$coderef]) |
|
|
354 | |
|
|
355 | When C<$coderef> is specified, it will be called from C<decode> each |
|
|
356 | time it decodes a JSON object. The only argument is a reference to the |
|
|
357 | newly-created hash. If the code references returns a single scalar (which |
|
|
358 | need not be a reference), this value (i.e. a copy of that scalar to avoid |
|
|
359 | aliasing) is inserted into the deserialised data structure. If it returns |
|
|
360 | an empty list (NOTE: I<not> C<undef>, which is a valid scalar), the |
|
|
361 | original deserialised hash will be inserted. This setting can slow down |
|
|
362 | decoding considerably. |
|
|
363 | |
|
|
364 | When C<$coderef> is omitted or undefined, C<decode> will not change the |
|
|
365 | deserialised hash in any way. This is maximally fast. |
|
|
366 | |
|
|
367 | Example, convert all JSON objects into the integer 5: |
|
|
368 | |
|
|
369 | my $js = JSON::XS->new->filter_json_object (sub { 5 }); |
|
|
370 | # returns [5] |
|
|
371 | $js->decode ('[{}]') |
|
|
372 | # throw an exception because allow_nonref is not enabled: |
|
|
373 | $js->decode ('{"a":1, "b":2}'); |
|
|
374 | |
|
|
375 | =item $json = $json->filter_json_single_key_object ([$coderef]) |
|
|
376 | |
|
|
377 | Works like C<filter_json_object>, but is only called for JSON objects |
|
|
378 | having only a single key. |
|
|
379 | |
|
|
380 | This C<$coderef> is called before the one specified via |
|
|
381 | C<filter_json_object>, if any. If it returns something, that will be |
|
|
382 | inserted into the data structure. If it returns nothing, the callback |
|
|
383 | from C<filter_json_object> will be called next. If you want to force |
|
|
384 | insertion of single-key objects even in the presence of a mutating |
|
|
385 | C<filter_json_object> callback, simply return the passed hash. |
|
|
386 | |
|
|
387 | As this callback gets called less often then the C<filter_json_object> |
|
|
388 | one, decoding speed will not usually suffer as much. Therefore, single-key |
|
|
389 | objects make excellent targets to serialise Perl objects into, especially |
|
|
390 | as single-key JSON objects are as close to the type-tagged value concept |
|
|
391 | as JSON gets (its basically an ID/VALUE tuple). Of course, JSON does not |
|
|
392 | support this in any way, so you need to make sure your data never looks |
|
|
393 | like a serialised Perl hash. |
|
|
394 | |
|
|
395 | Typical names for the single object key are C<__class_whatever__>, or |
|
|
396 | C<$__dollars_are_rarely_used__$> or C<}ugly_brace_placement>, or even |
|
|
397 | things like C<__class_md5sum(classname)__>, to reduce the risk of clashing |
|
|
398 | with real hashes. |
|
|
399 | |
|
|
400 | Example, decode JSON objects of the form C<< { "__widget__" => <id> } >> |
|
|
401 | into the corresponding C<< $WIDGET{<id>} >> object: |
|
|
402 | |
|
|
403 | # return whatever is in $WIDGET{5}: |
|
|
404 | JSON::XS |
|
|
405 | ->new |
|
|
406 | ->filter_json_single_key_object (sub { |
|
|
407 | exists $_[0]{__widget__} |
|
|
408 | ? $WIDGET{ $_[0]{__widget__} } |
|
|
409 | : () |
|
|
410 | }) |
|
|
411 | ->decode ('{"__widget__": 5') |
|
|
412 | |
|
|
413 | # this can be used with a TO_JSON method in some "widget" class |
|
|
414 | # for serialisation to json: |
|
|
415 | sub WidgetBase::TO_JSON { |
|
|
416 | my ($self) = @_; |
|
|
417 | |
|
|
418 | unless ($self->{id}) { |
|
|
419 | $self->{id} = ..get..some..id..; |
|
|
420 | $WIDGET{$self->{id}} = $self; |
|
|
421 | } |
|
|
422 | |
|
|
423 | { __widget__ => $self->{id} } |
|
|
424 | } |
| 352 | |
425 | |
| 353 | =item $json = $json->shrink ([$enable]) |
426 | =item $json = $json->shrink ([$enable]) |
| 354 | |
427 | |
| 355 | Perl usually over-allocates memory a bit when allocating space for |
428 | Perl usually over-allocates memory a bit when allocating space for |
| 356 | strings. This flag optionally resizes strings generated by either |
429 | strings. This flag optionally resizes strings generated by either |
| … | |
… | |
| 802 | still relatively early in its development. If you keep reporting bugs they |
875 | still relatively early in its development. If you keep reporting bugs they |
| 803 | will be fixed swiftly, though. |
876 | will be fixed swiftly, though. |
| 804 | |
877 | |
| 805 | =cut |
878 | =cut |
| 806 | |
879 | |
| 807 | our $true = do { bless \(my $dummy = 1), "JSON::XS::Boolean" }; |
880 | our $true = do { bless \(my $dummy = "1"), "JSON::XS::Boolean" }; |
| 808 | our $false = do { bless \(my $dummy = 0), "JSON::XS::Boolean" }; |
881 | our $false = do { bless \(my $dummy = "0"), "JSON::XS::Boolean" }; |
| 809 | |
882 | |
| 810 | sub true() { $true } |
883 | sub true() { $true } |
| 811 | sub false() { $false } |
884 | sub false() { $false } |
| 812 | |
885 | |
| 813 | sub is_bool($) { |
886 | sub is_bool($) { |
