paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 37 Packages Projects Releases Wiki Activity

frontend-app-api: add lazy external route ref resolution

Browse Source 
Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
This commit is contained in:
Patrik Oldsberg
2025-08-16 14:46:39 +02:00
parent a1127c8c93
commit 391f0ca10d
8 changed files with 126 additions and 70 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/frontend-system/architecture/36-routes.md
+1 -1
View File
@@ -279,7 +279,7 @@ Another thing to note is that this indirection in the routing is particularly us
### Default Targets for External Route References
It is possible to define a default target for an external route reference, potentially removing the need to bind the route in the app. This reduces the need for configuration when installing new plugins through providing a sensible default. It is of course still possible to override the route binding in the app.
It is possible to define a default target for an external route reference, potentially removing the need to bind the route in the app. This reduces the need for configuration when installing new plugins through providing a sensible default. It is of course still possible to override the route binding in the app, as long as the external route ref is exported via the `externalRoutes` property of the plugin instance.
The default target uses the same syntax as the route binding configuration, and will only be used if the target plugin and route exist. For example, this is how the catalog can define a default target for the create component external route in a way that removes the need for the binding in the previous example: