* 'master' of github.com:backstage/backstage: (98 commits)
build(deps): bump archiver from 5.0.2 to 5.1.0
build(deps): bump typescript-json-schema from 0.45.0 to 0.45.1
docs: Update lighthouse docs
scaffolder-backend: clarify type detection error message
scaffolder-backend: gitlab preparer uses integrations token
core-api: ensure that routable extension components are discovered at boot
core-api: memoize app element traversal and validation
core-api: add lazy loading of component extensions
Add changeset and add missing semicolon
Add search plugin to new CLI created apps
build(deps): bump graphql from 15.3.0 to 15.4.0
core-api: add MutableSessionManager and fix AuthSessionStore not properly updating session state
run prettier on the roadmap
core-api: refactor createReactExtension to forward component types directly and avoid @types/react dependency
core-api: add route validation to app + test
core-api: default type parameters for BackstagePlugin to avoid breakage
changeset: add changesets for new plugin extension API
core-api: avoid exporting AnyRoutes, AnyExternalRoutes, and ExternalRouteRef constructor
core-api: rename BindRouteFunc to AppRouteBinder
core-api,plugins/graphiql: export extension APIs from core-api and port the graphiql plugin
...
When a new Backstage app is setup, the techdocs backend file contains all the preparers (dir, github, gitlab, etc.) and same for generators. While this providers added customizibility, it comes with a cost of complexity in setting up the app backend. New preparers' updates would need users to update their app's techdocs backend file.
Scaffolder backend has already moved to this proposed pattern.
* This change adds an implementation for the readTree method in GitlabReader.
The implementation is similar to the readTree method in GithubReader
with the exception of the 'path' variable used for subpaths in the
archive. To facilitate this, GitlabIntegrationConfig now has an apiUrl
field which was missing for Gitlab but was present for Bitbucket & GH.
* As part of this change, there are also new tests added to GitlabReader
to mirror what has been done with the GH reader. For now the archive
format chosen is 'zip', follow-up action includes having a look at
whether tar.gz is preferable.
Signed-off-by: Matei David <madavid@expediagroup.com>
blam