Skip to content

Make it easier to avoid circular dependencies in Sf services #18

Description

@gggeek

As soon as you start declaring your Wrapper Repos as Sf services, because they require some other Sf service as dependency, it is quite easy to get into a situation of circular dependency.

This can be fixed by declaring services lazy, but it is both tedious and slows things down a bit at runtime.

Is there a better solution?

What if we f.e. allow to add 'service ids' into the Entity Manager as an alternative to injecting fully-built services?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions