You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're currently using the <EntityGithubInsightsReadmeCard/> in the default overview tab of the catalog component page.
While the readme renders correctly, we noticed that when pressing on any component in the Relations card, we get forwarded to this component but the readme stays the same as from the previous component.
This causes confusion as the wrong readme from the wrong component is loaded.
Expected Behavior
The correct corresponding readme is rendered when navigating to a different component from the Relations graph
Current Behavior
The old readme from the previous component is rendered
Steps to Reproduce
Include the <EntityGithubInsightsReadmeCard/> card in the overview tab of any component
Make sure this component has relations and are displayed in the Relations card
Press on any item in the Relations card
Backstage forwards me to the new component
The readme rendered there is from the old component
We're currently using the
<EntityGithubInsightsReadmeCard/>
in the default overview tab of the catalog component page.While the readme renders correctly, we noticed that when pressing on any component in the Relations card, we get forwarded to this component but the readme stays the same as from the previous component.
This causes confusion as the wrong readme from the wrong component is loaded.
Expected Behavior
The correct corresponding readme is rendered when navigating to a different component from the Relations graph
Current Behavior
The old readme from the previous component is rendered
Steps to Reproduce
<EntityGithubInsightsReadmeCard/>
card in the overview tab of any componentRelations
cardRelations
cardPossible Solution
Context
Your Environment
@backstage/plugin-catalog-react
version: 1.12.3@backstage/integration
version: 1.1.30 (integration-react)The text was updated successfully, but these errors were encountered: