teamneusta
diff --git a/‎README.md‎
Lines changed: 144 additions & 31 deletions b/‎README.md‎
Lines changed: 144 additions & 31 deletions
diff --git a/‎compose.yaml‎
Lines changed: 1 addition & 1 deletion b/‎compose.yaml‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎composer.json‎
Lines changed: 3 additions & 1 deletion b/‎composer.json‎
Lines changed: 3 additions & 1 deletion
diff --git a/‎config/pimcore/config.yaml‎
Lines changed: 3 additions & 63 deletions b/‎config/pimcore/config.yaml‎
Lines changed: 3 additions & 63 deletions
diff --git a/‎config/pimcore/export/assets/converters_populators.yaml‎
Lines changed: 95 additions & 0 deletions b/‎config/pimcore/export/assets/converters_populators.yaml‎
Lines changed: 95 additions & 0 deletions
@@ -3,57 +3,165 @@
 ## Installation
 
 1.  **Require the bundle**
-
+    
     ```shell
     composer require teamneusta/pimcore-import-export-bundle
     ```
 
-2. **Enable the bundle**
-
+2.  **Enable the bundle**
+    
     Add the Bundle to your `config/bundles.php`:
-
-   ```php
-   Neusta\Pimcore\ImportExportBundle\NeustaPimcoreImportExportBundle::class => ['all' => true],
-   ```
+    
+    ```php
+    Neusta\Pimcore\ImportExportBundle\NeustaPimcoreImportExportBundle::class => ['all' => true],
+    ```
 
 ## Usage
 
-After enabling the bundle you should see a new menu item in the context menu of Pimcore Admin Backend - Section Documents:
+### Pimcore Admin Backend
+
+#### Export
+
+After enabling the bundle you should see a new menu item in the context menu of Pimcore Admin Backend:
 
-![context_menu_import_export.png](docs/images/context_menu_import_export.png)
+| Documents | Assets                                                                              | Data Objects                                                                    |
+|--------|-------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|
+|![context_menu_export_assets.png](docs/images/context_menu_export_assets.png)| ![context_menu_export_documents.png](docs/images/context_menu_export_documents.png) | ![context_menu_export_objects.png](docs/images/context_menu_export_objects.png) |
+
+Currently only YAML Export is supported by menu
+
+After clicking one of the menu items you will be asked for a file name and the export will start:
+
+![filename_dialog.png](docs/images/filename_dialog.png)
 
 (german translation)
 
+##### Special case: Assets Export
+
+Because Assets are mostly assigned to physical files (images, videos, documents, etc.) the export will create a ZIP file containing the binary data and a YAML file with the metadata.
+The same structured zip file can be used for the import of Assets as well.
+
+#### Import
+For the import you can have a look into the Tools Menu:
+
+![import_menu.png](docs/images/import_menu.png)
+
+
+### Symfony Commands
+
+This bundle provides several commands to export and import data into Pimcore.
+
+Fur usage, run the commands with the `--help` option to see all available options and arguments.
+
+- `neusta:pimcore:export:documents`
+  - Export Pimcore documents (e.g., pages, snippets) to a YAML file. Export either the entire document tree or specific document IDs.
+- `neusta:pimcore:export:assets`
+  - Exports Pimcore assets (e.g., images, videos, PDFs) into two files: A YAML file along with a ZIP file containing the actual binary files.
+  - Both files share the same base name (e.g., `assets.yaml` and `assets.zip`).
+- `neusta:pimcore:export:objects`
+  - Exports Pimcore DataObjects into a YAML file. The objects can be filtered by ID or exported in full.
+- `neusta:pimcore:import:documents`
+  - Imports Pimcore documents (e.g., pages, snippets) from a YAML file.
+- `neusta:pimcore:import:assets`
+  - Imports assets (e.g., images, PDFs, videos) into Pimcore based on a YAML definition.
+  - The command expects a YAML file describing the assets and a ZIP archive containing the corresponding files. The ZIP file must be located in the same directory as the YAML file and must have the same base name (e.g., `assets.yaml` and `assets.zip`)
+- `neusta:pimcore:import:objects`
+  - Imports Pimcore DataObjects from a YAML file.
+
+#### Common Options
+
+All import commands follow a similar structure and support the following common options:
+
+- `--input` or `-i`: Path to the input YAML file (required for import commands).
+- `--dry-run`: Perform the operation without persisting data (only available for import commands).
+
+## Concepts
+
 ### Page Export
+
 The selected page will be exported into YAML format:
+
 ```yaml
-page:
-    id: 123
-    parentId: 1
-    type: page
-    published: true
-    path: /
-    language: de
-    navigation_name: my-site
-    navigation_title: 'My Site'
-    key: my-site
-    title: 'My Site'
-    controller: 'App\DefaultController::indexAction'
-    editables:
-        main:
-            type: areablock
-            name: main
-            data: [{ key: '1', type: text-editor, hidden: false }]
-...
+elements:
+    -
+        Pimcore\Model\Document:
+            id: 123
+            parentId: 1
+            type: page
+            published: true
+            path: /
+            language: de
+            navigation_name: my-site
+            navigation_title: 'My Site'
+            key: my-site
+            title: 'My Site'
+            controller: 'App\DefaultController::indexAction'
+            editables:
+                main:
+                    type: areablock
+                    name: main
+                    data: [ { key: '1', type: text-editor, hidden: false } ]
+# ...
 ```  
 
 In the same way you can re-import your yaml file again by selecting: `Import from YAML` in the context menu.
 
-## Configuration
-
 ### Page Import
 
-The import process will create a new page with the given data.
+The import process will create pages with the given data.
+
+The following rule applies:
+
+If the parseYaml method of the `PageImporter` is not called with `forcedSave`, the data from the provided YAML will be
+adopted, regardless of whether it makes sense or not, and without checking whether the page could be saved that way.
+
+ * If `forcedSave` is set to `true`, the ID will be retained (Caution – this can overwrite an existing page).
+ * If `forcedSave` is set to `true` and no ID has been set, it will be generated by Pimcore (Creating new page).
+
+ * If a `parentId` is specified, the corresponding document will be searched for.
+ * If it exists, it will be set as the parent (Note: This may override the `path` specification).
+ * If the `parentId` does not exist, an attempt will be made to find a parent using the `path` specification.
+ * If such a parent exists, the `parentId` will be set accordingly and saved.
+ * If neither is found, an InvalidArgumentException will be thrown, and the save operation will be aborted.
+
+![parent_flow.png](docs/images/parent_flow.png)
+
+If multiple pages are imported and a path specification changes by the applied rules, this path specification will be
+replaced with the new, correct path specification in all provided page configurations.
+
+### Parameterize your yaml files
+
+You can parameterize your yaml files with placeholders. The placeholders will be replaced by the values you provide in your fixtures.
+
+```yaml
+elements:
+    -
+        Pimcore\Model\Document:
+            id: 2
+            parentId: 1
+            # ...further properties
+            editables:
+              # ...several editables
+              'main:1.img:1.image':
+                  type: image
+                  data:
+                      id: %IMAGE_ID%
+              'main:1.img:1.title':
+              # ...
+```
+
+In the case above an image has been assigned to an `Editable/Image` editable. The image id is a placeholder `%IMAGE_ID%`.
+
+You can use now a `Neusta\Pimcore\ImportExportBundle\Documents\Import\Filter\SearchAndReplaceFilter` instance to replace the placeholder with the actual image id (e.g. 1234).
+
+```php
+$yamlContent = (new SearchAndReplaceFilter(['%IMAGE_ID%' => 1234]))->filterAndReplace($yamlContent);
+```
+
+If you want to change your yaml in a more complex way you can use the `Neusta\Pimcore\ImportExportBundle\Documents\Import\Filter\YamlFilter` interface to implement your own filter.
+
+With that technique you can export test pages for Fixtures, change values into placeholders (e.g. for assets and data objects) and replace them with the actual values in your tests.
+
 
 ## Contribution
 
@@ -74,5 +182,10 @@ We use composer scripts for our main quality tools. They can be executed via the
 ```shell
 bin/composer cs:fix
 bin/composer phpstan
-bin/composer tests
+```
+
+For the tests there is a different script, that includes a database setup.
+
+```shell
+bin/run-tests
 ```
@@ -16,7 +16,7 @@ services:
       timeout: 10s
 
   php:
-    image: pimcore/pimcore:php8.3-latest
+    image: pimcore/pimcore:php8.3-debug-latest
     volumes:
       - ./:/var/www/html/
     environment:
 
@@ -12,8 +12,9 @@
   ],
   "require": {
     "php": "~8.1.0 || ~8.2.0 || ~8.3.0",
+    "ext-zip": "*",
     "pimcore/pimcore": "^11.0",
-    "teamneusta/converter-bundle": "^1.7"
+    "teamneusta/converter-bundle": "^1.8.0"
   },
   "require-dev": {
     "ergebnis/composer-normalize": "^2.42.0",
@@ -25,6 +26,7 @@
     "phpstan/phpstan-symfony": "^1.3.8",
     "phpunit/phpunit": "^9.5",
     "pimcore/admin-ui-classic-bundle": "^1.6",
+    "spatie/phpunit-snapshot-assertions": "^4.2",
     "teamneusta/pimcore-testing-framework": "^0.12"
   },
   "autoload": {
 
@@ -1,63 +1,3 @@
-###########################################################
-# Neusta Converter Bundle
-###########################################################
-neusta_converter:
-  converter:
-    ###########################################################
-    # Import Converter (YamlExportPage -> Page)
-    ###########################################################
-    neusta_pimcore_import_export.import_page:
-      target: Pimcore\Model\Document\Page
-      populators:
-        - Neusta\Pimcore\ImportExportBundle\Documents\Import\PageImportPopulator
-      properties:
-        id:
-          source: id
-          skip_null: true
-          default: 0
-        key: ~
-        title:
-          source: title
-          default: 'no title'
-        controller:
-          source: controller
-          default: 'no controller'
-        type:
-          source: type
-          default: 'page'
-        published:
-          source: published
-          default: false
-        path:
-          source: path
-          default: '/'
-        parentId:
-          source: parentId
-          default: 0
-
-    ###########################################################
-    # Export Converter (Page -> YamlExportPage)
-    ###########################################################
-    neusta_pimcore_import_export.export_page:
-      target: Neusta\Pimcore\ImportExportBundle\Documents\Export\YamlExportPage
-      populators:
-        - neusta_pimcore_import_export.page.property.language.populator
-        - neusta_pimcore_import_export.page.property.navigation_title.populator
-        - neusta_pimcore_import_export.page.property.navigation_name.populator
-        - neusta_pimcore_import_export.page.editables.populator
-      properties:
-        id: ~
-        key: ~
-        title: ~
-        controller: ~
-        type: ~
-        published: ~
-        path: ~
-        parentId: ~
-
-    neusta_pimcore_import_export.editable_converter:
-      target: Neusta\Pimcore\ImportExportBundle\Documents\Export\YamlExportEditable
-      properties:
-        type: ~
-        name: ~
-        data: ~
+imports:
+    - { resource: 'import/**/*' }
+    - { resource: 'export/**/*' }
@@ -0,0 +1,95 @@
+###########################################################
+# Neusta Converter Bundle
+###########################################################
+neusta_converter:
+  converter:
+    ###########################################################
+    # Export Converter (Pimcore Asset -> Folder)
+    ###########################################################
+    neusta_pimcore_import_export.export_asset_folder:
+      target: Neusta\Pimcore\ImportExportBundle\Model\Asset\Asset
+      properties:
+        id: ~
+        key: ~
+        type: ~
+        path: ~
+        parentId: ~
+
+services:
+  _defaults:
+    autowire: true
+    autoconfigure: true
+
+  ###########################################################
+  # Export Converter (Pimcore Asset -> Asset)
+  ###########################################################
+  neusta_pimcore_import_export.strategy.export_asset:
+    class: Neusta\Pimcore\ImportExportBundle\Converter\TypeStrategyConverter
+    arguments:
+      $typeToConverterMap:
+        Pimcore\Model\Asset\Archive: '@neusta_pimcore_import_export.export_asset_archive'
+        Pimcore\Model\Asset\Audio: '@neusta_pimcore_import_export.export_asset_audio'
+        Pimcore\Model\Asset\Document: '@neusta_pimcore_import_export.export_asset_document'
+        Pimcore\Model\Asset\Image: '@neusta_pimcore_import_export.export_asset_image'
+        Pimcore\Model\Asset\Text: '@neusta_pimcore_import_export.export_asset_text'
+        Pimcore\Model\Asset\Video: '@neusta_pimcore_import_export.export_asset_video'
+        Pimcore\Model\Asset\Folder: '@neusta_pimcore_import_export.export_asset_folder'
+        Pimcore\Model\Asset\Unknown: '@neusta_pimcore_import_export.export_asset_unknown'
+
+  neusta_pimcore_import_export.export_asset_archive:
+    class: Neusta\Pimcore\ImportExportBundle\Converter\ExtendedConverter
+    arguments:
+      $converter: '@neusta_pimcore_import_export.export_asset_folder'
+      $postPopulators:
+        - '@neusta_pimcore_import_export.asset.filename.populator'
+
+  neusta_pimcore_import_export.export_asset_audio:
+    class: Neusta\Pimcore\ImportExportBundle\Converter\ExtendedConverter
+    arguments:
+      $converter: '@neusta_pimcore_import_export.export_asset_folder'
+      $postPopulators:
+        - '@neusta_pimcore_import_export.asset.filename.populator'
+
+  neusta_pimcore_import_export.export_asset_document:
+    class: Neusta\Pimcore\ImportExportBundle\Converter\ExtendedConverter
+    arguments:
+      $converter: '@neusta_pimcore_import_export.export_asset_folder'
+      $postPopulators:
+        - '@neusta_pimcore_import_export.asset.filename.populator'
+
+  neusta_pimcore_import_export.export_asset_image:
+    class: Neusta\Pimcore\ImportExportBundle\Converter\ExtendedConverter
+    arguments:
+      $converter: '@neusta_pimcore_import_export.export_asset_folder'
+      $postPopulators:
+        - '@neusta_pimcore_import_export.asset.filename.populator'
+
+  neusta_pimcore_import_export.export_asset_text:
+    class: Neusta\Pimcore\ImportExportBundle\Converter\ExtendedConverter
+    arguments:
+      $converter: '@neusta_pimcore_import_export.export_asset_folder'
+      $postPopulators:
+        - '@neusta_pimcore_import_export.asset.filename.populator'
+
+  neusta_pimcore_import_export.export_asset_video:
+    class: Neusta\Pimcore\ImportExportBundle\Converter\ExtendedConverter
+    arguments:
+      $converter: '@neusta_pimcore_import_export.export_asset_folder'
+      $postPopulators:
+        - '@neusta_pimcore_import_export.asset.filename.populator'
+
+  neusta_pimcore_import_export.export_asset_unknown:
+    class: Neusta\Pimcore\ImportExportBundle\Converter\ExtendedConverter
+    arguments:
+      $converter: '@neusta_pimcore_import_export.export_asset_folder'
+      $postPopulators: []
+
+  ###########################################################
+  # Export Populator (Pimcore Asset -> Asset)
+  ###########################################################
+  neusta_pimcore_import_export.asset.filename.populator:
+    class: Neusta\ConverterBundle\Populator\PropertyMappingPopulator
+    arguments:
+      $sourceProperty: filename
+      $targetProperty: filename
+