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

docs: clarify where extension creators should live

Browse Source 
Signed-off-by: Vincenzo Scamporlino <vincenzos@spotify.com>
This commit is contained in:
Vincenzo Scamporlino
2023-12-22 22:17:02 +01:00
parent 8e434302cd
commit 63f3a4c520
1 changed files with 2 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/frontend-system/architecture/03-extensions.md
+2 -7
View File
@@ -321,14 +321,9 @@ For more information on naming of extension refer to the [naming patterns docume
### Extension Creators in libraries
Extension creators should be exported from library packages (e.g. `*-react`, `*-common`) rather than plugin packages.
Extension creators should be exported from frontend library packages (e.g. `*-react`) rather than plugin packages.
<!--
Explain that extension creators should be exported from library packages (`-react`) rather than plugin packages.
philipph: What is the advantage - not super obvious to me from the comment. We would also need to change this e.g. for the catalog as it currently is exported from `catalog` alpha directly.
-->
If an extension is only for in-house tweaks, it's okay to put it in the plugin package. But if you want other open source plugins to use it, or you already have a `-react` package, always put extension creators in the `-react` package.
## Extension Boundary