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

Add missing angle brackets

Browse Source 
I'm new to Backstage, but this sentence doesn't seem to be calling attention to the package's owner/namespace/prefix. Therefore, it seems to intend `scope` as a variable, not an owner/namespace/prefix.

Signed-off-by: Jan Van Bruggen <JanCVanB@users.noreply.github.com>
This commit is contained in:
Jan Van Bruggen
2022-11-14 23:12:09 -07:00
committed by GitHub
parent f90dd68e78
commit 562f8bc6bb
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/overview/architecture-overview.md
+1 -1
View File
@@ -205,7 +205,7 @@ A typical plugin consists of up to five packages, two frontend ones, two
backend, and one isomorphic package. All packages within the plugin must share a
common prefix, typically of the form `@<scope>/plugin-<plugin-id>`, but
alternatives like `backstage-plugin-<plugin-id>` or
`@scope/backstage-plugin-<plugin-id>` are also valid. Along with this prefix,
`@<scope>/backstage-plugin-<plugin-id>` are also valid. Along with this prefix,
each of the packages have their own unique suffix that denotes their role. In
addition to these five plugin packages it's also possible for a plugin to have
additional frontend and backend modules that can be installed to enable optional