Skip to content

Resolve bidirectional dependencies #4

@dcadenas

Description

@dcadenas

When class A inherits, extends or includes class B we currently draw a dependency X from A to B.

A----->B
   X (inheritance/extension/inclusion)

We show a dependency Y from class B to class A when class B calls some method of class A (like in the template method pattern).

A<-----B
    Y

So in this cases the relationship between class A and B becomes bidirectional.

A<---->B
   X+Y

The diagram would be clearer if we remove dependency Y and just leave X, given that we somehow indicate that dependency X is based on inheritance/extension/inclusion.

So this feature will be done after issue #3

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions