With the following example setup, a circular dependency is created - is there a way to avoid this?

Content type: Product
- Field: Content - paragraph field
-- Allowed paragraphs: Related products

Paragraph type: Related products
- Field: Related products - entity reference field
-- Available bundles: Product content

The content type requires the paragraph, but the paragraph requires the content type. These get created as two different features (with Paragraphs as a base plugin type, which I've seen recommended in other threads), so we end up with a circular dependency.

I guess you could have the same with content types that reference each other.

We could bundle them together as they are a product feature together, but that's not always the case - this is just a simple example. Consider if there were several content types that allow a paragraph that can reference any of those content types.

Comments

smaz created an issue. See original summary.

nedjo’s picture

You might try looking at using one more more configuration templates via Config Actions.

nedjo’s picture

Status: Active » Fixed

This looks like a support request that was answered. Please feel free to reopen if otherwise.

Status: Fixed » Closed (fixed)

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

Pasqualle’s picture

If entity reference field is part of the circular dependency, then you can manually remove the dependencies of the entity reference field, which are used for "Available bundles". If the bundle does not exists it can't be referenced, Drupal will not throw any error. As soon as the bundle exists it can be referenced.