All files / realm/blong-access index.browser.ts

0% Statements 0/142
0% Branches 0/1
0% Functions 0/1
0% Lines 0/142

Press n or j to go to the next uncovered block, b, p or k for the previous block.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143                                                                                                                                                                                                                                                                                             
import {browser} from '@feasibleone/blong';
import pkg from './package.json' with {type: 'json'};

/**
 * index.browser.ts — standalone browser bootstrap for blong-access.
 *
 * Wires the built-in blong-browser realm (portal, RPC, auth) around the access
 * realm so the access model pages (Browse/New/Open) can run against the live
 * server, e.g. for the Playwright suite of this package.
 *
 * It names no other page-owning realm. It used to load blong-realm for its
 * hand-written pages, and that made the two packages depend on each other — each
 * suite loaded the other's realm, which Rush rejects as a workspace cycle. The
 * composed portal is still proved, by the realms that host more than one: the
 * gateway and suite packages load both and assert the merged menu
 * (`test/portalMerge.play.ts`).
 */
export default browser(blong => ({
    url: import.meta.url,
    pkg: {
        name: pkg.name,
        version: pkg.version,
    },
    validation: blong.type.Object({
        login: blong.type.Object({}),
        access: blong.type.Object({}),
    }),
    children: [
        /** Built-in blong-browser realm: RPC, auth, portal, auth orchestrators */
        async function ui() {
            return import('@feasibleone/blong-browser/browser.ts');
        },
        /** blong-login browser realm — `login.*` subject namespace (login.token.* etc.) */
        async function login() {
            return import('@feasibleone/blong-login/browser.ts');
        },
        /** blong-access realm (brings the access models + browser namespace) */
        async function access() {
            return import('./browser.ts');
        },
    ],
    config: {
        default: {
            ui: {
                portal: {
                    portal: {
                        title: 'Blong Access',
                        // Self-service profile: the top-right account menu
                        // (`page`) opens the profile tab, and fetches the
                        // caller's own profile (`get`) for the avatar initials.
                        profile: {
                            page: 'access.user.profile',
                            get: 'access.profile.get',
                        },
                        // Per-language translation dictionaries.  blong-browser
                        // registers them at boot and `setLanguage(language)`
                        // (driven by the user's preferred language returned at
                        // login) swaps the active table to the matching
                        // language's dictionary — English uses an empty dict
                        // (fall back to the English strings).
                        translations: {
                            en: {},
                            bg: {
                                Profile: 'Профил',
                                'Sign out': 'Отписване',
                                'First Name': 'Собствено име',
                                'Last Name': 'Фамилия',
                                Email: 'Имейл',
                                'Preferred Language': 'Предпочитан език',
                                'Profile saved': 'Профилът е запазен',
                                Save: 'Запази',
                                'Change Password': 'Смяна на парола',
                                'Current Password': 'Текуща парола',
                                'New Password': 'Нова парола',
                                'Confirm New Password': 'Потвърди новата парола',
                                'Password changed': 'Паролата е сменена',
                                Roles: 'Роли',
                                'No roles assigned': 'Няма присвоени роли',
                                'Passwords do not match': 'Паролите не съвпадат',
                                Active: 'Активен',
                                Inactive: 'Неактивен',
                            },
                        },
                        // UI languages offered by the menubar language switcher
                        // (ad-hoc, client-side switching).  `value` matches a
                        // translation-dictionary key above.
                        languages: [
                            {value: 'en', label: 'English'},
                            {value: 'bg', label: 'Български'},
                        ],
                    },
                },
            },
            blong: {},
            login: {},
            access: {},
        },
        // TEST-ONLY: the `integration` intent (active in the browser for
        // dev/test/Playwright runs — the browser entry `index.html.ts`
        // hardcodes `microservice integration dev`) enables the test hook that
        // exposes the wrapped handler as `window.__blongHandler` (gated in
        // BlongContext by `portal.testHook`) so E2E tests can invoke server
        // methods directly.  Production uses the `prod` intent — never
        // `integration` — so real deployments do not expose the handler.
        // (The cast is a framework typing limitation: non-default intent
        // blocks only type the realm's own validation keys, while child-realm
        // config like `ui` is allowed at runtime via `activeConfigs`.)
        integration: {
            ui: {
                portal: {
                    portal: {
                        testHook: true,
                    },
                },
            },
        } as never,
        'test-ui': {
            ui: {
                portal: {
                    portal: {
                        menu: [
                            {
                                id: 'test',
                                title: 'Test',
                                items: [
                                    {
                                        title: 'Test runs',
                                        method: 'access.test.run',
                                        icon: 'pi pi-play',
                                    },
                                ],
                            },
                        ],
                    },
                },
            },
            blong: {},
            login: {},
            access: {},
        } as never,
    },
}));