docs/releases/v1.28.0-next.2-changelog.md
Upgrade Helper: https://backstage.github.io/upgrade-helper/?to=1.28.0-next.2
readTree for Harness provider to support TechDocs functionalitydropDatabasereadTree for Harness provider to support TechDocs functionality863a800: Added the following default targets for external routes:
createComponent binds to the Scaffolder page.viewTechDoc binds to the TechDocs entity documentation page.createFromTemplate binds to the Scaffolder selected template page.60085dd: Added the following default targets for external routes:
registerComponent binds to the catalog import page.viewTechDoc binds to the TechDocs entity documentation page.fetchApi implementation for event source requests. This allows you to for example, override the Authorization header.dropDatabaseTokenManagerService and IdentityService types as deprecatedTestDatabases to no longer depend on backend-common35fbe09: Added support for configuration of route bindings through static configuration, and default targets for external route refs.
In addition to configuring route bindings through code, it is now also possible to configure route bindings under the app.routes.bindings key, for example:
app:
routes:
bindings:
catalog.createComponent: catalog-import.importPage
Each key in the route binding object is of the form <plugin-id>.<externalRouteName>, where the route name is key used in the externalRoutes object passed to createPlugin. The value is of the same form, but with the name taken from the plugin routes option instead.
The equivalent of the above configuration in code is the following:
const app = createApp({
// ...
bindRoutes({ bind }) {
bind(catalogPlugin.externalRoutes, {
createComponent: catalogImportPlugin.routes.importPage,
});
},
});
Updated dependencies
SidebarSubmenu text to not follow the theme colorSelect component.SupportButton where the title was rendered with the characteristics of a button.defaultTarget option to createExternalRouteRef. I lets you specify a default target of the route by name, for example 'catalog.catalogIndex', which will be used if the target route is present in the app and there is no explicit route binding.5.4.node-gyp to v10registerComponent external route will now by default bind to the catalog import page if it is available.catalogEntity external route will now by default bind to the catalog entity page if it is available.catalogIndex external route is now optional and will by default bind to the catalog index page if it is available.tokenManager definition from @backstage/backend-plugin-apigitlab:issue:edit action to edit existing GitLab issuesfetchApi implementation for event source requests. This allows you to for example, override the Authorization header.