The description in the Entry was mapped to the latest timeline entry, which is a changelog. This
change maps the description in the API to the entry. To maintain backwards compatibility it
will set the description to the last timeline entry if no description exists at the entry level.
Signed-off-by: Niall McCullagh <niallmccullagh@users.noreply.github.com>
If an entry has both a radar description and an external url, when
a user clicks on the blip the description dialog would briefly
appear before they are redirected to the specified url.
Expected behaviour is not to automatically redirect the user so that
they can read the dialog and choose to follow the link for more details.
Signed-off-by: Niall McCullagh <mccullagh_niall@hotmail.com>
Signed-off-by: Niall McCullagh <niallmccullagh@users.noreply.github.com>
This adds a new app.support top level config that can be used to
configure various support links and other information. This can later be
extended for plugins to append their own specific support items.
As part of the refactor to include entry history the moved and url attributes were
no longer being mapped. This resulted in the radar not indicating if an entry had moved,
and the bubble not being clickable.
* 'master' of github.com:spotify/backstage: (139 commits)
Cleanup
Update PinButton.test.tsx
feat: update github insights plugin version (#2973)
Ignore IntelliJ *.iml files (#2971)
chore(deps): bump rollup-plugin-dts from 1.4.11 to 1.4.13
fix the plugin card on plugins page
align 'Add to Marketplace' button on plugins page
fix the PluginGrid on mobiles sizes
use getBy query instead of queryBy when asserting for elements present in document (#2951)
Update PinButton.tsx
Add test case for Progress component (#2953)
fix the styling of footer copy on mobile
add changeset
handle the case where no entities are available to show
core-api: work around issue with ApiRef export const declarations
core-api: move utility api system implementation into apis/system
Update docs regarding npm config ignore-scripts flag
Another try
Fix Core Features configuration id (#2948)
Fix test?
...
* remove data-testid from div
* add test case for Progress component
* add changeset
* update the GraphiQLPage test cases to handle Progress timeout
* update the RadarComponent and RadarPage test case to handle Progress timeout
* update the TechDocsProgressBar test case to handle Progress timeout
* add changeset
github-actions[bot]