Support for configuration entities

pushed to 2.0.x
thanks

Automatically closed - issue fixed for 2 weeks with no activity.

Thank you all on pushing this feature forward.
I'm testing it and can see that more or less code works, but fails on the save.
For example, I have menu as reference and want to create new and save it.
On save action I'm getting:
TypeError: Drupal\inline_entity_form\ReferenceUpgrader::upgradeEntityReferences(): Argument #1 ($entity) must be of type Drupal\Core\Entity\FieldableEntityInterface, Drupal\system\Entity\Menu given, called in /var/www/docroot/modules/contrib/inline_entity_form/src/WidgetSubmit.php on line 57 in Drupal\inline_entity_form\ReferenceUpgrader->upgradeEntityReferences() (line 46 of /var/www/docroot/modules/contrib/inline_entity_form/src/ReferenceUpgrader.php)
That is because, code of the reference save was hard-coded to work with content entities.
We have to add config entity support here:
https://git.drupalcode.org/project/inline_entity_form/-/blob/8.x-1.x/src...

@anpolimus can you create a new issue ticket as follow up ?

Issue will be created, no worries. I'm also involved in this fix

Link to new issue: https://www.drupal.org/project/inline_entity_form/issues/3365747 🐛 ConfigEntityReference error during creation of the new referenced entity Closed: outdated

Bulk reopen.

This urgently needs tests before any commit. As the issue tag sais.

Hi ,

I referenced another issue asking for complex support
https://www.drupal.org/project/inline_entity_form/issues/3228086#comment... 💬 Adding complex widget to custom config entity form Active

I pushed a rebased version of 3.0 on this branch issue , I do not know drupal git policies are okay with that

proceeding to some tests

PS2: gitlab doesnt appreciate this trickery and generates a patch incompatible with "lockable" composer version , here is a patch of pure difference (not incremental as gitlab proposes)