@embedpdf/plugin-link 3.0.0-next.14 → 3.0.0-next.16

package/dist/contract-DGKEPl11.cjs

@@ -1,11 +0,0 @@
-//#region src/types.ts
-const LinkToken = (0, require("@embedpdf/core").createCapabilityToken)("link");
-//#endregion
-Object.defineProperty(exports, "LinkToken", {
-	enumerable: true,
-	get: function() {
-		return LinkToken;
-	}
-});
-
-//# sourceMappingURL=contract-DGKEPl11.cjs.map

package/dist/contract-DGKEPl11.cjs.map

@@ -1 +0,0 @@
-{"version":3,"file":"contract-DGKEPl11.cjs","names":[],"sources":["../src/types.ts"],"sourcesContent":["import { createCapabilityToken, type PageObjectNumber } from '@embedpdf/core';\nimport type {\n  AnnotationRef,\n  PdfActionTree,\n  PdfDestination,\n  PdfLinkTarget,\n} from '@embedpdf/engine-core/runtime';\nimport type { ActionDispatchResult } from '@embedpdf/plugin-actions/contract';\nimport type { LinkNavItem } from '@embedpdf/plugin-annotation/contract';\n\nexport type { LinkNavItem };\n// The wire target vocabulary, re-exported so app code building link editors\n// needs only this package (the annotation-props precedent).\nexport type { PdfDestination, PdfLinkTarget };\n\n/**\n * What one activation did. `revealed` = the stage moved the camera;\n * `destination` = no stage plugin — the embedder gets the explicit\n * destination to handle; `uri` = opening is the FRAMEWORK layer's job (the\n * plugin is DOM-free); `named` = a viewer verb (NextPage…) reported until\n * stage verbs land; `reported` = read-only/executable-shaped targets\n * (javascript / goto-remote / launch / unsupported) — surfaced, NEVER\n * executed here (javascript belongs to the scripting orchestrator).\n */\nexport type LinkActivation =\n  | { outcome: 'revealed' }\n  | { outcome: 'destination'; destination: PdfDestination }\n  | { outcome: 'uri'; uri: string }\n  | { outcome: 'named'; name: string }\n  | { outcome: 'reported'; target: PdfLinkTarget }\n  /** The action engine took the activation (full payload tree, mixed /Next\n   *  chains included). `dispatch` is the in-flight result; the framework\n   *  opener must do NOTHING for this outcome — the actions UI adapter owns\n   *  any URI open (the no-double-open rule). */\n  | { outcome: 'dispatched'; dispatch: Promise<ActionDispatchResult> }\n  | { outcome: 'none' };\n\n/** Optional activation context: the payload-carrying /A tree (and its\n *  annotation identity) from the LinkNavItem, enabling action-engine\n *  delegation. Without it — or without the actions plugin — activation\n *  follows the classic root-projection path. */\nexport interface LinkActivateContext {\n  activate?: PdfActionTree;\n  ref?: AnnotationRef;\n  pon?: PageObjectNumber;\n}\n\nexport interface LinkActivateEvent {\n  target: PdfLinkTarget;\n  activation: LinkActivation;\n}\n\nexport interface LinkPluginConfig {\n  /** Every activation (navigations AND reported targets) — analytics /\n   *  custom handling. Called after the built-in handling ran. */\n  onActivate?: (event: LinkActivateEvent) => void;\n}\n\n/**\n * The navigation plane of link annotations. Data comes from ONE of two\n * sources, picked at init: the annotation plugin's folded model when that\n * plugin is present (zero extra engine reads — it already lists every\n * page), or the plugin's own engine reads in viewer-only deployments.\n */\nexport interface LinkCapability {\n  /** The clickable link areas of a page (content space, y-down). */\n  linksOn(pon: PageObjectNumber): LinkNavItem[];\n  /** Lazy-load a page's links (no-op when the annotation plugin owns the data). */\n  ensurePage(pon: PageObjectNumber): void;\n  /** Whether the navigation plane currently owns links: the active tool\n   *  enables `link-nav` (pointer/pan/form-fill by default). While false —\n   *  the link tool or any authoring tool is active — the annotation plane\n   *  owns them and the LinkLayer stands down. */\n  engaged(): boolean;\n  /** THE one activation entry point (framework layers call it on click). */\n  activate(target: PdfLinkTarget, context?: LinkActivateContext): LinkActivation;\n}\n\n/** Engine-backed page cache (viewer-only deployments). */\nexport interface LinkState {\n  pages: Record<number, LinkNavItem[]>;\n}\n\nexport type LinkAction =\n  | { type: 'SET_PAGE'; pon: number; items: LinkNavItem[] }\n  | { type: 'DROP_PAGE'; pon: number };\n\nexport const LinkToken = createCapabilityToken<LinkCapability>('link');\n"],"mappings":";AAuFA,MAAa,aAAA,2BAAA,CAAA,CAAA,sBAAA,CAAkD,MAAM"}

package/dist/contract-DO3vDsAV.d.cts

@@ -1,92 +0,0 @@
-import { PageObjectNumber } from "@embedpdf/core";
-import { AnnotationRef, PdfActionTree, PdfDestination, PdfLinkTarget } from "@embedpdf/engine-core/runtime";
-import { ActionDispatchResult } from "@embedpdf/plugin-actions/contract";
-import { LinkNavItem } from "@embedpdf/plugin-annotation/contract";
-//#region src/types.d.ts
-/**
- * What one activation did. `revealed` = the stage moved the camera;
- * `destination` = no stage plugin — the embedder gets the explicit
- * destination to handle; `uri` = opening is the FRAMEWORK layer's job (the
- * plugin is DOM-free); `named` = a viewer verb (NextPage…) reported until
- * stage verbs land; `reported` = read-only/executable-shaped targets
- * (javascript / goto-remote / launch / unsupported) — surfaced, NEVER
- * executed here (javascript belongs to the scripting orchestrator).
- */
-type LinkActivation = {
-  outcome: 'revealed';
-} | {
-  outcome: 'destination';
-  destination: PdfDestination;
-} | {
-  outcome: 'uri';
-  uri: string;
-} | {
-  outcome: 'named';
-  name: string;
-} | {
-  outcome: 'reported';
-  target: PdfLinkTarget;
-} |
-/** The action engine took the activation (full payload tree, mixed /Next
- *  chains included). `dispatch` is the in-flight result; the framework
- *  opener must do NOTHING for this outcome — the actions UI adapter owns
- *  any URI open (the no-double-open rule). */
-{
-  outcome: 'dispatched';
-  dispatch: Promise<ActionDispatchResult>;
-} | {
-  outcome: 'none';
-};
-/** Optional activation context: the payload-carrying /A tree (and its
- *  annotation identity) from the LinkNavItem, enabling action-engine
- *  delegation. Without it — or without the actions plugin — activation
- *  follows the classic root-projection path. */
-interface LinkActivateContext {
-  activate?: PdfActionTree;
-  ref?: AnnotationRef;
-  pon?: PageObjectNumber;
-}
-interface LinkActivateEvent {
-  target: PdfLinkTarget;
-  activation: LinkActivation;
-}
-interface LinkPluginConfig {
-  /** Every activation (navigations AND reported targets) — analytics /
-   *  custom handling. Called after the built-in handling ran. */
-  onActivate?: (event: LinkActivateEvent) => void;
-}
-/**
- * The navigation plane of link annotations. Data comes from ONE of two
- * sources, picked at init: the annotation plugin's folded model when that
- * plugin is present (zero extra engine reads — it already lists every
- * page), or the plugin's own engine reads in viewer-only deployments.
- */
-interface LinkCapability {
-  /** The clickable link areas of a page (content space, y-down). */
-  linksOn(pon: PageObjectNumber): LinkNavItem[];
-  /** Lazy-load a page's links (no-op when the annotation plugin owns the data). */
-  ensurePage(pon: PageObjectNumber): void;
-  /** Whether the navigation plane currently owns links: the active tool
-   *  enables `link-nav` (pointer/pan/form-fill by default). While false —
-   *  the link tool or any authoring tool is active — the annotation plane
-   *  owns them and the LinkLayer stands down. */
-  engaged(): boolean;
-  /** THE one activation entry point (framework layers call it on click). */
-  activate(target: PdfLinkTarget, context?: LinkActivateContext): LinkActivation;
-}
-/** Engine-backed page cache (viewer-only deployments). */
-interface LinkState {
-  pages: Record<number, LinkNavItem[]>;
-}
-type LinkAction = {
-  type: 'SET_PAGE';
-  pon: number;
-  items: LinkNavItem[];
-} | {
-  type: 'DROP_PAGE';
-  pon: number;
-};
-declare const LinkToken: import("@embedpdf/core").CapabilityToken<LinkCapability>;
-//#endregion
-export { LinkCapability as a, LinkState as c, PdfLinkTarget as d, LinkActivation as i, LinkToken as l, LinkActivateContext as n, LinkNavItem as o, LinkActivateEvent as r, LinkPluginConfig as s, LinkAction as t, PdfDestination as u };
-//# sourceMappingURL=contract-DO3vDsAV.d.cts.map

package/dist/contract-HRggERzU.js

@@ -1,7 +0,0 @@
-import { createCapabilityToken } from "@embedpdf/core";
-//#region src/types.ts
-const LinkToken = createCapabilityToken("link");
-//#endregion
-export { LinkToken as t };
-
-//# sourceMappingURL=contract-HRggERzU.js.map

package/dist/contract-HRggERzU.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"contract-HRggERzU.js","names":[],"sources":["../src/types.ts"],"sourcesContent":["import { createCapabilityToken, type PageObjectNumber } from '@embedpdf/core';\nimport type {\n  AnnotationRef,\n  PdfActionTree,\n  PdfDestination,\n  PdfLinkTarget,\n} from '@embedpdf/engine-core/runtime';\nimport type { ActionDispatchResult } from '@embedpdf/plugin-actions/contract';\nimport type { LinkNavItem } from '@embedpdf/plugin-annotation/contract';\n\nexport type { LinkNavItem };\n// The wire target vocabulary, re-exported so app code building link editors\n// needs only this package (the annotation-props precedent).\nexport type { PdfDestination, PdfLinkTarget };\n\n/**\n * What one activation did. `revealed` = the stage moved the camera;\n * `destination` = no stage plugin — the embedder gets the explicit\n * destination to handle; `uri` = opening is the FRAMEWORK layer's job (the\n * plugin is DOM-free); `named` = a viewer verb (NextPage…) reported until\n * stage verbs land; `reported` = read-only/executable-shaped targets\n * (javascript / goto-remote / launch / unsupported) — surfaced, NEVER\n * executed here (javascript belongs to the scripting orchestrator).\n */\nexport type LinkActivation =\n  | { outcome: 'revealed' }\n  | { outcome: 'destination'; destination: PdfDestination }\n  | { outcome: 'uri'; uri: string }\n  | { outcome: 'named'; name: string }\n  | { outcome: 'reported'; target: PdfLinkTarget }\n  /** The action engine took the activation (full payload tree, mixed /Next\n   *  chains included). `dispatch` is the in-flight result; the framework\n   *  opener must do NOTHING for this outcome — the actions UI adapter owns\n   *  any URI open (the no-double-open rule). */\n  | { outcome: 'dispatched'; dispatch: Promise<ActionDispatchResult> }\n  | { outcome: 'none' };\n\n/** Optional activation context: the payload-carrying /A tree (and its\n *  annotation identity) from the LinkNavItem, enabling action-engine\n *  delegation. Without it — or without the actions plugin — activation\n *  follows the classic root-projection path. */\nexport interface LinkActivateContext {\n  activate?: PdfActionTree;\n  ref?: AnnotationRef;\n  pon?: PageObjectNumber;\n}\n\nexport interface LinkActivateEvent {\n  target: PdfLinkTarget;\n  activation: LinkActivation;\n}\n\nexport interface LinkPluginConfig {\n  /** Every activation (navigations AND reported targets) — analytics /\n   *  custom handling. Called after the built-in handling ran. */\n  onActivate?: (event: LinkActivateEvent) => void;\n}\n\n/**\n * The navigation plane of link annotations. Data comes from ONE of two\n * sources, picked at init: the annotation plugin's folded model when that\n * plugin is present (zero extra engine reads — it already lists every\n * page), or the plugin's own engine reads in viewer-only deployments.\n */\nexport interface LinkCapability {\n  /** The clickable link areas of a page (content space, y-down). */\n  linksOn(pon: PageObjectNumber): LinkNavItem[];\n  /** Lazy-load a page's links (no-op when the annotation plugin owns the data). */\n  ensurePage(pon: PageObjectNumber): void;\n  /** Whether the navigation plane currently owns links: the active tool\n   *  enables `link-nav` (pointer/pan/form-fill by default). While false —\n   *  the link tool or any authoring tool is active — the annotation plane\n   *  owns them and the LinkLayer stands down. */\n  engaged(): boolean;\n  /** THE one activation entry point (framework layers call it on click). */\n  activate(target: PdfLinkTarget, context?: LinkActivateContext): LinkActivation;\n}\n\n/** Engine-backed page cache (viewer-only deployments). */\nexport interface LinkState {\n  pages: Record<number, LinkNavItem[]>;\n}\n\nexport type LinkAction =\n  | { type: 'SET_PAGE'; pon: number; items: LinkNavItem[] }\n  | { type: 'DROP_PAGE'; pon: number };\n\nexport const LinkToken = createCapabilityToken<LinkCapability>('link');\n"],"mappings":";;AAuFA,MAAa,YAAY,sBAAsC,MAAM"}