thuecat/Classes/Domain/Import/EntityMapper.php
Daniel Siepmann bfd4c77a17 Refactor parsing of JSON-LD
Use Symfony components to map incoming JSON onto objects.
Those provide a mapping. They can then be used to fetch the data in a
common way and insert it into the system.

- Handle languages within JsonDecode
  (normalize incoming data based on language)
- Handle Single Value and List of Values within Entities. They will map
  incoming Data to proper Objects. (We now generally transform during
  serialization process if target is array but we got single entity)
- Add missing tests for existing data.
- Finish migration of all existing data, this includes next step
- Provide discriminator to ObjectNormalizer to auto detect target class
  based on "type" property. (Done for now by own registry)
- Combine generated object with current structure for import -> generate
  data array out of it.
- Resolve foreign references to existing entities,
  (images, contentresponsible, etc.)
2021-08-12 09:46:37 +02:00

97 lines
3.4 KiB
PHP

<?php
declare(strict_types=1);
/*
* Copyright (C) 2021 Daniel Siepmann <coding@daniel-siepmann.de>
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
* as published by the Free Software Foundation; either version 2
* of the License, or (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
* 02110-1301, USA.
*/
namespace WerkraumMedia\ThueCat\Domain\Import;
use Symfony\Component\PropertyInfo\Extractor\PhpDocExtractor;
use Symfony\Component\PropertyInfo\Extractor\ReflectionExtractor;
use Symfony\Component\PropertyInfo\PropertyInfoExtractor;
use Symfony\Component\Serializer\Encoder\JsonEncoder;
use Symfony\Component\Serializer\Normalizer\DateTimeNormalizer;
use Symfony\Component\Serializer\Normalizer\ObjectNormalizer;
use Symfony\Component\Serializer\Serializer;
use WerkraumMedia\ThueCat\Domain\Import\EntityMapper\ArrayDenormalizer;
use WerkraumMedia\ThueCat\Domain\Import\EntityMapper\JsonDecode;
use WerkraumMedia\ThueCat\Domain\Import\EntityMapper\MappingException;
class EntityMapper
{
/**
* Returns mapped entity.
* The returned object is of type $targetClassName
*/
public function mapDataToEntity(
array $jsonLD,
string $targetClassName,
array $context
): object {
$serializer = $this->createSerializer();
try {
return $serializer->deserialize(
json_encode($jsonLD),
$targetClassName,
'json',
$context
);
} catch (\Throwable $e) {
throw new MappingException($jsonLD, $targetClassName, $e);
}
}
private function createSerializer(): Serializer
{
return new Serializer(
[
new ArrayDenormalizer(),
new DateTimeNormalizer(),
new ObjectNormalizer(
null,
null,
null,
// We enforce following behaviour:
// 1. Try to fetch info via reflection (e.g. by methods or property)
// 2. Use php doc as fallback
// We do this because of:
// Most of the time we can just use the TypeHint of setter or add/remove for collections
// Sometimes we have to deal with multiple types (e.g. string and array)
// We then can have a different property name and no type hint, reflection will fail
// But we can use PHPDoc to define all supported
new PropertyInfoExtractor(
[],
[
new ReflectionExtractor(),
new PhpDocExtractor(),
]
)
),
],
[
new JsonEncoder(
null,
new JsonDecode()
),
]
);
}
}