@lotics/app-sdk 0.100.1 → 0.101.1

package/dist/src/viewer.d.ts

@@ -1,26 +0,0 @@
-/**
- * Read the app's context once, shared across every hook via a stable SWR key.
- * The host (the product iframe, or `lotics app dev`) supplies the signed-in
- * member and the app's declared capabilities.
- */
-export declare function useAppContext(): {
-    memberId: string | null;
-    commentsEnabled: boolean;
-    recordingEnabled: boolean;
-    resolved: boolean;
-};
-/**
- * The signed-in member currently viewing the app — the **view-as target** under
- * an admin's "View as" (product UI or `lotics app dev --view-as`), the
- * authenticated member otherwise, and `null` for a public/standalone visitor or
- * until the context resolves (gate viewer-dependent UI on `loading`).
- *
- * Use it to personalize (greet the member, default an assignment to them) or to
- * pass the viewer into a workflow that must attribute to them. **Per-row data
- * scoping does NOT need this** — put an `is_current_member` filter in the query
- * template and the server resolves it to the same member (honoring view-as).
- */
-export declare function useViewer(): {
-    memberId: string | null;
-    loading: boolean;
-};

package/dist/src/viewer.js

@@ -1,47 +0,0 @@
-import useSWR from "swr";
-import { rpc } from "./rpc.js";
-import { readRecordingSnapshot, replaceRecordings } from "./recording_state.js";
-/**
- * The context, with its recording snapshot applied in the same task the
- * answer arrived in — before any later host push is handled, so the snapshot
- * can never overwrite a newer push.
- */
-async function fetchContext() {
-    const context = await rpc("context", {});
-    replaceRecordings(readRecordingSnapshot(context.recordings));
-    return context;
-}
-/**
- * Read the app's context once, shared across every hook via a stable SWR key.
- * The host (the product iframe, or `lotics app dev`) supplies the signed-in
- * member and the app's declared capabilities.
- */
-export function useAppContext() {
-    const { data } = useSWR("app-context", fetchContext, {
-        revalidateOnFocus: false,
-        revalidateIfStale: false,
-        revalidateOnReconnect: false,
-        shouldRetryOnError: false,
-    });
-    return {
-        memberId: data?.member_id ?? null,
-        commentsEnabled: data?.comments_enabled ?? false,
-        recordingEnabled: data?.recording_enabled === true,
-        resolved: data !== undefined,
-    };
-}
-/**
- * The signed-in member currently viewing the app — the **view-as target** under
- * an admin's "View as" (product UI or `lotics app dev --view-as`), the
- * authenticated member otherwise, and `null` for a public/standalone visitor or
- * until the context resolves (gate viewer-dependent UI on `loading`).
- *
- * Use it to personalize (greet the member, default an assignment to them) or to
- * pass the viewer into a workflow that must attribute to them. **Per-row data
- * scoping does NOT need this** — put an `is_current_member` filter in the query
- * template and the server resolves it to the same member (honoring view-as).
- */
-export function useViewer() {
-    const ctx = useAppContext();
-    return { memberId: ctx.memberId, loading: !ctx.resolved };
-}