dependencyOf relationship is one-sided in the UI

Expected Behavior

1. Specify a dependencyOf relationship indicating that component A is a dependency of component B.
2. Visit component B in the UI.
3. I expect the EntityDepdendsOnComponentsCard to list component A.

This behavior is what happens when I instead specify that component B dependsOn component A.

Current Behavior

Component A is not listed.

Possible solution

1. Fix the code (😄 )

Steps to Reproduce

1. Load this catalog-info file into Backstage.
2. Ensure the EntityDepdendsOnComponentsCard is present in the UI
3. Visit the passenger-backend service.

Here’s a video showing me reproducing the problem.

Context

I’m trying to indicate dependencies between components in Backstage.

Your Environment

I’m using latest master as of today to reproduce this.

[andrewthauer]

I fell into tree same trap actually. We have a shared db resource that I thought it would be quicker and easier to use dependencyOf instead of going to each component using it and saying dependsOn. I then realized it didn’t work the opposite way.

[gmambro]

I fell into tree same trap actually. We have a shared db resource that I thought it would be quicker and easier to use dependencyOf instead of going to each component using it and saying dependsOn. I then realized it didn’t work the opposite way.

+1