Skip to content

pattern to extend a service definition and aliasing new definition to the old name #5920

Closed
@lsmith77

Description

@lsmith77

i keep stumbling over this use case:

https://github.com/liip/LiipFunctionalTestBundle/pull/70/files#L7R25
https://github.com/liip/LiipFunctionalTestBundle/pull/70/files#L1R13

what is the best practice here? is there one? is there something that we could change to make this easier? specifically i would love to avoid duplicating the definition. guess we could clone the original test.client definition in the extension?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions