Files
TREK/plugin-sdk/test/permissions-parity.test.ts
jubnl 1e6ab069cd Fix/sdk default (#2199)
* feat(plugin-sdk): settings-field default + unknown-attribute warning

* feat(shared): default on the plugin settings-field contract

* feat(server): persist and serve plugin settings-field defaults

* feat(client): pre-fill plugin settings defaults in the admin and user forms

* feat(server): enforce required plugin settings on both save paths

* feat(client): block plugin-settings save on an empty required field

* feat(server): resolve plugin settings defaults at runtime

A settings-field `default` was stored and served to the form but never
reached the plugin: the child's init envelope, `ctx.settings.get()`, the
channel dispatch's readAll and the OAuth provider config all read the
stored blob only. Fold `stored ?? default` in on every path that hands
config to a plugin (settings-defaults.ts), and let a default satisfy
`required` on both save gates — refusing a save the runtime would have
accepted was a contradiction.

Also: one `isFilled` rule shared by the save gate and `hasRequired`
(checkbox exempt, whitespace empty); the install parser drops a
non-boolean checkbox default or a select default outside its options,
matching what the SDK already refuses; export SETTING_FIELD_KEYS so the
SDK's mirror can be parity-tested.

* feat(client): share the plugin settings form rules across all three forms

The mobile user settings screen was a third consumer of the fields/config
contract that never got `default` pre-fill or the required check, and
the seed/patch loops lived in five hand copies. Extract
seedSettingsValues / findMissingRequired / settingsPatch into one module
and use it from the admin instance form, the desktop user tab and the
mobile screen. The user forms now surface a 4xx `{ error }` from the
server (the required-field refusal) instead of the generic toast.

* feat(plugin-sdk): seed dev fixtures from manifest defaults

`trek-plugin dev` handed the plugin only the fixture values, so a plugin
relying on its manifest defaults read undefined in dev and only in dev.
Seed ctx.config / ctx.settings from the declared defaults (a fixture
value still wins) via a new exported settingDefaults(manifest, scope).
SETTING_FIELD_KEYS is now parity-tested against the host's list.

* docs(plugins): document settings defaults as runtime fallbacks

A `default` is the field's effective value wherever nobody set one, not
just a form pre-fill; `required` is enforced on both ends; unknown
attributes are dropped at install and warned on by validate. Add a
Settings section with the attribute table to the SDK README and update
the ctx type comments, the shared schema, and the wiki guide.

* add missing exports
2026-09-02 18:42:16 +02:00

113 lines
6.6 KiB
TypeScript

/**
* The hook->permission map is no longer hand-mirrored: gen-plugin-facts.ts generates
* src/generated/host-facts.ts from the server's protocol/envelope.ts, and that
* generator's --check mode is a CI gate. What is still hand-vendored here is the
* pure egress-policy helpers. trek-plugin-sdk ships standalone and cannot import across
* the package boundary, so the copies are real copies — and a silent drift here is the
* worst possible bug in this module: `dev` would confidently green-light a plugin that
* the host then refuses (or refuse one the host would allow).
*
* These tests read the server's source directly. They only run inside the TREK monorepo;
* in a published/standalone checkout the server isn't there and they skip.
*/
import { describe, it, expect } from 'vitest';
import fs from 'node:fs';
import path from 'node:path';
import { fileURLToPath } from 'node:url';
import { HOOK_PERMISSION } from '../src/permissions.js';
import { SETTING_FIELD_KEYS } from '../src/manifest.js';
import { PLUGIN_SESSION_MAX_KEYS, PLUGIN_SESSION_MAX_KEY_LENGTH, PLUGIN_SESSION_MAX_VALUE_BYTES, EVENT_FAMILIES, EVENT_SNAPSHOT_GRANT, KNOWN_PERMISSIONS } from '../src/index.js';
const here = path.dirname(fileURLToPath(import.meta.url));
const serverPlugins = path.resolve(here, '../../server/src/nest/plugins');
const envelopeFile = path.join(serverPlugins, 'protocol/envelope.ts');
const serverEgress = path.join(serverPlugins, 'runtime/egress-policy.ts');
const inMonorepo = fs.existsSync(envelopeFile) && fs.existsSync(serverEgress);
const hostFrame = path.resolve(here, '../../client/src/components/Plugins/PluginFrame.tsx');
describe.skipIf(!inMonorepo)('parity with the host', () => {
it("the generated host facts match the server's envelope.ts", () => {
// Not a regex scrape any more: server/scripts/gen-plugin-facts.ts imports envelope.ts
// and writes src/generated/host-facts.ts, and its --check mode is a CI gate. This
// asserts the checked-in artefact is the one the host would produce, so a standalone
// publish (which has no server present) still ships the right list.
//
// Compared as whole maps, both ways round: asserting the artefact merely CONTAINS
// each entry passed when the host grew a hook the artefact never learned about,
// which is the drift that actually ships a wrong permission list.
const envelope = fs.readFileSync(envelopeFile, 'utf8');
const block = envelope.match(/HOOK_PERMISSION[^{]*\{([\s\S]*?)\n\}/);
expect(block, 'HOOK_PERMISSION not found in envelope.ts').toBeTruthy();
const theirs: Record<string, string> = {};
for (const m of block![1].matchAll(/^\s*(\w+):\s*'([^']+)'/gm)) theirs[m[1]] = m[2];
expect(theirs).toEqual({ ...HOOK_PERMISSION });
expect(Object.keys(HOOK_PERMISSION).length).toBeGreaterThan(0);
});
it('the vendored egress-policy helpers are byte-identical to the server\'s', () => {
const ours = fs.readFileSync(path.resolve(here, '../src/egress-policy.ts'), 'utf8');
const theirs = fs.readFileSync(serverEgress, 'utf8');
// Compare the pure helpers only — our file additionally carries installEgressGuard
// (the server's lives in plugin-host-entry.ts, where it is coupled to the child).
const fns = ['isBlockedIp', 'expandV6', 'makeHostAllow', 'dgramSendTarget', 'dgramConnectTarget', 'unwrapConnectArgs', 'classifyConnect'];
const body = (src: string, name: string): string => {
const start = src.indexOf(`function ${name}(`);
expect(start, `${name} not found`).toBeGreaterThan(-1);
// From the signature to the closing brace at column 0 — these are all top-level fns.
const end = src.indexOf('\n}', start);
return src.slice(start, end).replace(/\s+/g, ' ').trim();
};
for (const fn of fns) expect(body(ours, fn), `${fn} has drifted from the server`).toBe(body(theirs, fn));
});
});
describe.skipIf(!fs.existsSync(hostFrame))('parity with the host frame', () => {
it('the session storage contract is one contract in all three copies', () => {
// Nothing generates these: the limits are written out by hand in the SDK export
// authors import, in the dev preview's inlined host, and in the real frame, because
// the SDK ships standalone and cannot import across the package boundary. Bump one
// and the preview happily stores what production then rejects.
const frame = fs.readFileSync(hostFrame, 'utf8');
const devServer = fs.readFileSync(path.resolve(here, '../src/cli/dev.ts'), 'utf8');
expect(frame).toContain(`const PLUGIN_SESSION_MAX_KEYS = ${PLUGIN_SESSION_MAX_KEYS}`);
expect(frame).toContain(`const PLUGIN_SESSION_MAX_KEY_LENGTH = ${PLUGIN_SESSION_MAX_KEY_LENGTH}`);
expect(frame).toContain(`const PLUGIN_SESSION_MAX_VALUE_BYTES = ${PLUGIN_SESSION_MAX_VALUE_BYTES}`);
expect(devServer).toContain(
`SESSION_MAX_KEYS=${PLUGIN_SESSION_MAX_KEYS},SESSION_MAX_KEY_LENGTH=${PLUGIN_SESSION_MAX_KEY_LENGTH},SESSION_MAX_VALUE_BYTES=${PLUGIN_SESSION_MAX_VALUE_BYTES}`,
);
// Same for the codes a plugin branches on — a rename in one copy is a silent
// behaviour change for anyone who developed against the other.
for (const code of ['SESSION_INVALID_KEY', 'SESSION_INVALID_VALUE', 'SESSION_VALUE_TOO_LARGE', 'SESSION_KEY_LIMIT', 'NO_TRIP_CONTEXT', 'SESSION_STORAGE_ERROR']) {
expect(frame, `${code} missing from the host frame`).toContain(`'${code}'`);
expect(devServer, `${code} missing from the dev preview`).toContain(`"${code}"`);
}
});
});
describe.skipIf(!inMonorepo)('core event catalog', () => {
it('event snapshot grants are known read permissions on known families', () => {
expect(EVENT_FAMILIES.length).toBeGreaterThan(0);
for (const [family, perm] of Object.entries(EVENT_SNAPSHOT_GRANT)) {
expect(EVENT_FAMILIES).toContain(family);
expect(KNOWN_PERMISSIONS).toContain(perm);
}
});
});
describe.skipIf(!inMonorepo)('settings-field attribute parity', () => {
it("SETTING_FIELD_KEYS matches the host's install/manifest.ts", () => {
// The `manifest.settings-known-keys` check warns on an attribute the host would
// silently drop, so the list must be the host's — compared whole, both ways round.
const theirsFile = path.resolve(here, '../../server/src/nest/plugins/install/manifest.ts');
const src = fs.readFileSync(theirsFile, 'utf8');
const block = src.match(/export const SETTING_FIELD_KEYS = \[([\s\S]*?)\] as const/);
expect(block, 'SETTING_FIELD_KEYS not found in install/manifest.ts').toBeTruthy();
const theirs = [...block![1].matchAll(/'([^']+)'/g)].map((m) => m[1]);
expect([...SETTING_FIELD_KEYS]).toEqual(theirs);
});
});