All records which are not saved or useable are now skipped.
Some records were converted but could not be stored, e.g. because no
localization was configured for that table.
This should bring small performance improvement and also align import
log with actually imported (converted) records.
Logging is added as well, only debug level, to allow developer and
integrator to analyse why some records are skipped.
Ignore some errors which don't actually exist.
We already check type of entity, and logger is always injected.
Catch the exception and return null.
That is already a possible return type which should be handled by
callers.
Add test case with referenced 404 image.
- Removed individual converters for TYPO3.
Conversion is now handled in a single converter.
- The new converter will import necessary dependencies upfront, e.g.
town or organisation.
- Move import state into extra class.
Relates: #34
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.)
This should ensure rendering works as expected.
Most important: This ensures data is available in frontend templates.
Add dev dependency to fluid_styled_content. This is necessary to test
our rendering integration with fluid_styled_content defaults.
Relates: #34
Import Configuration can now be stored on folders, beside the site root.
That way editors can create and edit records.
The default storage pid for new records can be defined via TypoScript.
Resolves: #24
That's necessary as models grow.
Added features should be tested to not break with future changes.
The tests revealed an existing error in fallback which got fixed to make
new test pass.
Relates: #18
