Frontend: Update Portal route examples in comments to /portal

This commit is contained in:
Michael Mayer 2026-06-10 04:39:26 +00:00
parent bf9866750f
commit d34284994d
3 changed files with 3 additions and 3 deletions

View file

@ -93,7 +93,7 @@ export function instancePath(siteUrl) {
// persistInstanceIdentity records this instance's SiteUrl, display title, app icon,
// and frontend route in the given (namespaced) store, so other instances on the same
// origin can list it in the navigation instance switcher and open it at its app entry
// point. The route is the frontend URI (e.g. "/portal/admin" or "/i/pro-1/library");
// point. The route is the frontend URI (e.g. "/portal" or "/i/pro-1/library");
// the switcher opens it so a web-overlay landing page at the site root is bypassed.
// No-op without a URL or usable store.
export function persistInstanceIdentity(store, identity) {

View file

@ -479,7 +479,7 @@ export default class Session {
persistInstanceIdentity(this.storage, {
url: values.siteUrl,
// Frontend URI (e.g. "/portal/admin" or "/i/pro-1/library") so peers open the
// Frontend URI (e.g. "/portal" or "/i/pro-1/library") so peers open the
// app entry point rather than a web-overlay landing page at the site root.
route: this.config?.frontendUri,
title: instanceLabel(values.siteUrl) || values.siteTitle || values.name || values.siteUrl,

View file

@ -90,7 +90,7 @@ export default {
}
},
// onSwitch navigates the browser to the selected instance's app entry point
// (its frontend route, e.g. /i/pro-1/library or /portal/admin) so the user lands
// (its frontend route, e.g. /i/pro-1/library or /portal) so the user lands
// in the app instead of a web-overlay landing page; its own login then completes
// the standard OIDC flow when a session is required. Falls back to the SiteUrl.
onSwitch(instance) {