Handle exceptions during import

needs reroll after #3098095: Remove deprecated code and declare 9.0 compatibility

1. +++ b/default_content.services.yml
   @@ -13,3 +13,6 @@ services:
   +  logger.channel.default_content:
   

   new service needs post_update hook to rebuild container

2. +++ b/src/Importer.php
   @@ -100,8 +109,16 @@ class Importer implements ImporterInterface {
   +                              LoggerInterface $logger = NULL) {
   
   @@ -109,6 +126,14 @@ class Importer implements ImporterInterface {
   +    $this->logger = $this->createLogger($logger);
   

   nor sure it needs this BC, I found no other contrib which overrrides the service

I've recently created the 2.0.x branch, see the project page on all the improvements in the 2.0.x branch. The 1.x branch isn't actively maintained and won't receive new features anymore, so moving this over to 2.0.x. Agree that this would be good to have.

Will need a reroll however.

Rerolled the patch in #11 to 2.0.x.

Do you really want to continue with importing potential broken content? I'm thinking instead we should use transactions, and rollback all content being imported if any exception occur.

Moreover to broken content you can also get commits from dblog or custom modules.

Trying to use transactions is very fragile way with a tons of workarounds and compromise... I'd say just throw exception and fix content or code

Rerolled the patch in #13 to the latest version of 2.0.x.

Patch in #16 fails against the latest dev release.

Rerolled the patch in #16 to the latest version of 2.0.x.

Rerolled the patch in #17 to the latest version of 2.0.x