pocketmine / netresearch-jsonmapper
Fork of netresearch/jsonmapper with security fixes needed by pocketmine/pocketmine-mp
Requires
- php: >=7.1
- ext-json: *
- ext-pcre: *
- ext-reflection: *
- ext-spl: *
Requires (Dev)
- phpunit/phpunit: ~7.5 || ~8.0 || ~9.0 || ~10.0
- squizlabs/php_codesniffer: ~3.5
Replaces
- netresearch/jsonmapper: ~4.2.0
- dev-fork
- v4.4.999
- v4.2.1000
- v4.2.999
- v4.2.0
- v4.1.0
- v4.0.0
- v3.1.1
- v3.1.0
- v3.0.0
- v2.1.0
- v2.0.0
- v1.6.0
- v1.5.2
- v1.5.1
- v1.5.0
- v1.4.0
- v1.3.0
- v1.2.0
- v1.1.1
- v1.1.0
- v1.0.0
- v0.11.0
- v0.10.0
- v0.9.0
- v0.8.0
- v0.7.0
- v0.6.1
- v0.6.0
- v0.5.0
- v0.4.4
- v0.4.3
- v0.4.2
- v0.4.1
- v0.4.0
- v0.3.0
- v0.2.1
- v0.2.0
- v0.1.3
- v0.1.2
- v0.1.1
- v0.1.0
- dev-dependabot/composer/phpunit/phpunit-tw-11.4.0
- dev-dependabot/github_actions/actions/cache-4
- dev-dependabot/github_actions/actions/checkout-4
- dev-strict-object-checking
- dev-master
- dev-null-in-arrays
- dev-array-in-string-property-error
This package is auto-updated.
Last update: 2024-12-03 15:21:05 UTC
README
Takes data retrieved from a JSON web service and converts them into nested object and arrays - using your own model classes.
Starting from a base object, it maps JSON data on class properties, converting them into the correct simple types or objects.
It's a bit like the native SOAP parameter mapping PHP's SoapClient
gives you, but for JSON.
It does not rely on any schema, only your PHP class definitions.
Type detection works by parsing @var
docblock annotations of
class properties, as well as type hints in setter methods.
You do not have to modify your model classes by adding JSON specific code; it works automatically by parsing already-existing docblocks.
This library has no dependencies.
Keywords: deserialization, hydration
Contents
Pro & contra
Benefits
- Autocompletion in IDEs
- It's easy to add comfort methods to data model classes
- Your JSON API may change, but your models can stay the same - not breaking applications that use the model classes.
Drawbacks
Model classes need to be written by hand
Since JsonMapper does not rely on any schema information (e.g. from json-schema), model classes cannot be generated automatically.
Usage
Basic usage
- Register an autoloader that can load PSR-0 compatible classes.
- Create a
JsonMapper
object instance - Call the
map
ormapArray
method, depending on your data
Map a normal object:
<?php require 'autoload.php'; $mapper = new JsonMapper(); $contactObject = $mapper->map($jsonContact, new Contact()); // or as classname $contactObject = $mapper->map($jsonContact, Contact::class); ?>
Map an array of objects:
<?php require 'autoload.php'; $mapper = new JsonMapper(); $contactsArray = $mapper->mapArray( $jsonContacts, array(), 'Contact' ); ?>
Instead of array()
you may also use ArrayObject
and descending classes
as well as classes implementing ArrayAccess
.
Example
JSON from an address book web service:
{ 'name':'Sheldon Cooper', 'address': { 'street': '2311 N. Los Robles Avenue', 'city': 'Pasadena' } }
Your local Contact
class:
<?php class Contact { /** * Full name * @var string */ public $name; /** * @var Address */ public $address; } ?>
Your local Address
class:
<?php class Address { public $street; public $city; public function getGeoCoords() { //do something with $street and $city } } ?>
Your application code:
<?php $json = json_decode(file_get_contents('http://example.org/sheldon.json')); $mapper = new JsonMapper(); $contact = $mapper->map($json, new Contact()); echo "Geo coordinates for " . $contact->name . ": " . var_export($contact->address->getGeoCoords(), true); ?>
Property type mapping
JsonMapper
uses several sources to detect the correct type of
a property:
The setter method (
set
+ucwords($propertyname)
) is inspected.Underscores "
_
" and hyphens "-
" make the next letter uppercase. Propertyfoo_bar-baz
leads to setter methodsetFooBarBaz
.If it has a type hint in the method signature then its type used:
public function setPerson(Contact $person) {...}
The method's docblock is inspected for
@param $type
annotations:/** * @param Contact $person Main contact for this application */ public function setPerson($person) {...}
If no type could be detected, the plain JSON value is passed to the setter method.
Class property types (since PHP 7.4):
public Contact $person;
Constructor property promotion types (since PHP 8.0):
public function __construct(protected Contact $person) {}
@var $type
docblock annotation of class properties:/** * @var \my\application\model\Contact */ public $person;
The property has to be public to be used directly. You may also use $bIgnoreVisibility to utilize protected and private properties.
If no type could be detected, the property gets the plain JSON value set.
If a property can not be found, JsonMapper tries to find the property in a case-insensitive manner. A JSON property
isempty
would then be mapped to a PHP propertyisEmpty
.Note
You have to provide the fully qualified namespace for the type to work. Relative class names are evaluated in the context of the current classes namespace, NOT respecting any imports that may be present.
PHP does not provide the imports via Reflection; the comment text only contains the literal text of the type. For performance reasons JsonMapper does not parse the source code on its own to detect and expand any imports.
Supported type names
Simple types
string
bool
,boolean
int
,integer
double
,float
array
object
mixed
Class names, with and without namespaces
Contact
- exception will be thrown if the JSON value isnull
Arrays of simple types and class names:
int[]
Contact[]
Multidimensional arrays:
int[][]
TreeDeePixel[][][]
ArrayObjects of simple types and class names:
ContactList[Contact]
NumberList[int]
Backed enums, with and without namespaces
Suit:string|Suit:int
- exception will be thrown if the JSON value is not present in the enum
Nullable types:
int|null
- will benull
if the value in JSON isnull
, otherwise it will be an integerContact|null
- will benull
if the value in JSON isnull
, otherwise it will be an object of typeContact
ArrayObjects and extending classes are treated as arrays.
Variables without a type or with type mixed
will get the
JSON value set directly without any conversion.
See phpdoc's type documentation for more information.
Simple type mapping
When an object shall be created but the JSON contains a simple type only (e.g. string, float, boolean), this value is passed to the classes' constructor. Example:
PHP code:
/** * @var DateTime */ public $date;
JSON:
{"date":"2014-05-15"}
This will result in new DateTime('2014-05-15')
being called.
Class map
When variables are defined as objects of abstract classes or interfaces, JsonMapper would normally try to instantiate those directly and crash.
Using JsonMapper's $classMap
property, you can specify which classes
shall get instantiated instead:
$jm = new JsonMapper(); $jm->classMap['Foo'] = 'Bar'; $jm->map(...);
This would create objects of type Bar
when a variable is defined to be
of type Foo
.
It is also possible to use a callable in case the actual implementation class needs to be determined dynamically (for example in case of a union). The mapped class ('Foo' in the example below) and the Json data are passed as parameters into the call.
$mapper = function ($class, $jvalue) { // examine $class and $jvalue to figure out what class to use... return 'DateTime'; }; $jm = new JsonMapper(); $jm->classMap['Foo'] = $mapper; $jm->map(...);
Nullables
JsonMapper throws an exception when a JSON property is null
,
unless the PHP class property has a nullable type - e.g. Contact|null
.
If your API contains many fields that may be null
and you do not want
to make all your type definitions nullable, set:
$jm->bStrictNullTypes = false;
Logging
JsonMapper's setLogger()
method supports all PSR-3 compatible
logger instances.
Events that get logged:
- JSON data contain a key, but the class does not have a property or setter method for it.
- Neither setter nor property can be set from outside because they are protected or private
Handling invalid or missing data
During development, APIs often change. To get notified about such changes, JsonMapper can be configured to throw exceptions in case of either missing or yet unknown data.
Unknown properties
When JsonMapper sees properties in the JSON data that are
not defined in the PHP class, you can let it throw an exception
by setting $bExceptionOnUndefinedProperty
:
$jm = new JsonMapper(); $jm->bExceptionOnUndefinedProperty = true; $jm->map(...);
You may also choose to handle those properties yourself by setting
a callable to $undefinedPropertyHandler
:
/** * Handle undefined properties during JsonMapper::map() * * @param object $object Object that is being filled * @param string $propName Name of the unknown JSON property * @param mixed $jsonValue JSON value of the property * * @return void */ function setUndefinedProperty($object, $propName, $jsonValue) { $object->{'UNDEF' . $propName} = $jsonValue; } $jm = new JsonMapper(); $jm->undefinedPropertyHandler = 'setUndefinedProperty'; $jm->map(...);
Or if you would let JsonMapper handle the setter for you, you can return a string
from the $undefinedPropertyHandler
which will be used as property name.
/** * Handle undefined properties during JsonMapper::map() * * @param object $object Object that is being filled * @param string $propName Name of the unknown JSON property * @param mixed $jsonValue JSON value of the property * * @return void */ function fixPropName($object, $propName, $jsonValue) { return ucfirst($propName); } $jm = new JsonMapper(); $jm->undefinedPropertyHandler = 'fixPropName'; $jm->map(...);
Missing properties
Properties in your PHP classes can be marked as "required" by
putting @required
in their docblock:
/** * @var string * @required */ public $someDatum;
When the JSON data do not contain this property, JsonMapper will throw
an exception when $bExceptionOnMissingData
is activated:
$jm = new JsonMapper(); $jm->bExceptionOnMissingData = true; $jm->map(...);
Option $bRemoveUndefinedAttributes
causes JsonMapper to remove properties
from the final object if they have not been in the JSON data:
$jm = new JsonMapper(); $jm->bRemoveUndefinedAttributes = true; $jm->map(...);
Private properties and functions
You can allow mapping to private and protected properties and
setter methods by setting $bIgnoreVisibility
to true:
$jm = new JsonMapper(); $jm->bIgnoreVisibility = true; $jm->map(...);
Simple types instead of objects
When a variable's type is a class and JSON data is a simple type
like string
, JsonMapper passes this value to the class' constructor.
If you do not want this, set $bStrictObjectTypeChecking
to true
:
$jm = new JsonMapper(); $jm->bStrictObjectTypeChecking = true; $jm->map(...);
An exception is then thrown in such cases.
Passing arrays to map()
You may wish to pass array data into map()
that you got by calling
json_decode($jsonString, true)
By default, JsonMapper will throw an exception because map()
requires
an object as first parameter.
You can circumvent that by setting $bEnforceMapType
to false
:
$jm = new JsonMapper(); $jm->bEnforceMapType = false; $jm->map(...);
Post-mapping callback
JsonMapper is able to call a custom method directly on each object after mapping it is finished:
$jm = new JsonMapper(); $jm->postMappingMethod = 'afterMapping'; $jm->map(...);
Now afterMapping()
is called on each mapped object
(if the class has that method).
You may pass additional arguments to the post-mapping callback:
$jm = new JsonMapper(); $jm->postMappingMethod = 'afterMapping'; $jm->postMappingMethodArguments = [23, 'foo']; $jm->map(...);
Installation
Via Composer from Packagist:
$ composer require netresearch/jsonmapper
Related software
Alternatives
- Jackson's data binding for Java
- Johannes Schmitt Serializer for PHP
- metassione for PHP
- Cartographer for PHP
- Data Transfer Object for PHP
- Valinor for PHP
- An equally named JsonMapper library that has dependencies.
About JsonMapper
License
JsonMapper is licensed under the OSL 3.0.
Coding style
JsonMapper follows the PEAR Coding Standards.