From 61ec305259cb3bf146a78c8520a5d6c0cd9543cb Mon Sep 17 00:00:00 2001 From: David de Boer Date: Mon, 16 Nov 2026 20:31:44 +0100 Subject: [PATCH] =?UTF-8?q?docs(search):=20say=20why=20a=20lookup=E2=80=99?= =?UTF-8?q?s=20local=20copy=20stays=20opt-in?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Derived and from lookups yield bare ids, with no referent node to copy - Literal lookups store strings beside their referents, which a nested copy cannot sit beside - A target built from the referring document’s own graph would only be stored twice --- packages/search/src/schema.ts | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/packages/search/src/schema.ts b/packages/search/src/schema.ts index 6601ab4d..cc02573a 100644 --- a/packages/search/src/schema.ts +++ b/packages/search/src/schema.ts @@ -322,6 +322,13 @@ export type ReferenceStrategy = * rather than an id – and because framing must reach one step further to * read the target’s fields off the referent * ({@link inlineFramingDepth}). A schema that declares none pays neither. + * + * And opt-in because not every lookup has a copy worth storing. A + * `derive`d or `from` lookup yields ids with no referent node behind + * them. A `literal` lookup stores strings beside its referents, which a + * nested object cannot sit beside. A lookup whose target documents are + * built from the same graph as the referring one – a register’s + * publisher – would only store each of them twice. */ readonly local?: boolean; /**