@agnostack/next-shopify 4.0.0-canary.8 → 4.0.0

package/dist/storage/index.d.ts

@@ -1,61 +0,0 @@
-/**
- * Shop and session ids are nullable: `sanitizeShop` returns null for anything it does not
- * recognise, and the core forwards that rather than guarding.
- *
- * @typedef {string | null | undefined} ShopId
- */
-/**
- * What the session layer needs from a store. Two entities, sessions and state, both scoped to a
- * shop. Nothing here is Firestore-specific: `@agnostack/next-shopify/firestore` is one
- * implementation, and an app can supply its own.
- *
- * ⚠️ Values arrive ALREADY ENCRYPTED and already stripped of anything that must not be persisted.
- * An implementation stores and returns what it is handed - it must not inspect, reshape or
- * re-encrypt, or the core's crypto and DPA guarantees stop holding.
- *
- * ⚠️ `findSessionIds` returns `[]` rather than erroring for an unknown shop - that is what an
- * initial install looks like.
- *
- * @typedef {object} SessionStorage
- * @property {(shopId: ShopId, sessionId: ShopId) => Promise<any>} loadSession
- * @property {(shopId: ShopId, session: any) => Promise<any>} updateSession
- *   MERGES into the stored session. The core writes partial sessions, so a replacing write
- *   would silently drop fields it did not send.
- * @property {(shopId: ShopId, sessionIds: any) => Promise<any>} deleteSessions
- * @property {(shopId: ShopId) => Promise<string[]>} findSessionIds
- * @property {(shop: ShopId) => Promise<any>} loadState
- * @property {(shop: ShopId, state: any) => Promise<any>} storeState
- * @property {(shop: ShopId) => Promise<any>} deleteState
- */
-export const STORAGE_METHODS: string[];
-export function ensureStorage(storage: any): SessionStorage;
-/**
- * Shop and session ids are nullable: `sanitizeShop` returns null for anything it does not
- * recognise, and the core forwards that rather than guarding.
- */
-export type ShopId = string | null | undefined;
-/**
- * What the session layer needs from a store. Two entities, sessions and state, both scoped to a
- * shop. Nothing here is Firestore-specific: `@agnostack/next-shopify/firestore` is one
- * implementation, and an app can supply its own.
- *
- * ⚠️ Values arrive ALREADY ENCRYPTED and already stripped of anything that must not be persisted.
- * An implementation stores and returns what it is handed - it must not inspect, reshape or
- * re-encrypt, or the core's crypto and DPA guarantees stop holding.
- *
- * ⚠️ `findSessionIds` returns `[]` rather than erroring for an unknown shop - that is what an
- * initial install looks like.
- */
-export type SessionStorage = {
-    loadSession: (shopId: ShopId, sessionId: ShopId) => Promise<any>;
-    /**
-     *   MERGES into the stored session. The core writes partial sessions, so a replacing write
-     *   would silently drop fields it did not send.
-     */
-    updateSession: (shopId: ShopId, session: any) => Promise<any>;
-    deleteSessions: (shopId: ShopId, sessionIds: any) => Promise<any>;
-    findSessionIds: (shopId: ShopId) => Promise<string[]>;
-    loadState: (shop: ShopId) => Promise<any>;
-    storeState: (shop: ShopId, state: any) => Promise<any>;
-    deleteState: (shop: ShopId) => Promise<any>;
-};

package/dist/storage/index.js

@@ -1,58 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.ensureStorage = exports.STORAGE_METHODS = void 0;
-const index_js_1 = require("../shared/index.js");
-/**
- * Shop and session ids are nullable: `sanitizeShop` returns null for anything it does not
- * recognise, and the core forwards that rather than guarding.
- *
- * @typedef {string | null | undefined} ShopId
- */
-/**
- * What the session layer needs from a store. Two entities, sessions and state, both scoped to a
- * shop. Nothing here is Firestore-specific: `@agnostack/next-shopify/firestore` is one
- * implementation, and an app can supply its own.
- *
- * ⚠️ Values arrive ALREADY ENCRYPTED and already stripped of anything that must not be persisted.
- * An implementation stores and returns what it is handed - it must not inspect, reshape or
- * re-encrypt, or the core's crypto and DPA guarantees stop holding.
- *
- * ⚠️ `findSessionIds` returns `[]` rather than erroring for an unknown shop - that is what an
- * initial install looks like.
- *
- * @typedef {object} SessionStorage
- * @property {(shopId: ShopId, sessionId: ShopId) => Promise<any>} loadSession
- * @property {(shopId: ShopId, session: any) => Promise<any>} updateSession
- *   MERGES into the stored session. The core writes partial sessions, so a replacing write
- *   would silently drop fields it did not send.
- * @property {(shopId: ShopId, sessionIds: any) => Promise<any>} deleteSessions
- * @property {(shopId: ShopId) => Promise<string[]>} findSessionIds
- * @property {(shop: ShopId) => Promise<any>} loadState
- * @property {(shop: ShopId, state: any) => Promise<any>} storeState
- * @property {(shop: ShopId) => Promise<any>} deleteState
- */
-exports.STORAGE_METHODS = [
-    'loadState',
-    'storeState',
-    'deleteState',
-    'loadSession',
-    'updateSession',
-    'deleteSessions',
-    'findSessionIds'
-];
-/**
- * Fails at composition rather than at the first OAuth round-trip. Nothing automated covers the
- * Shopify auth flow, so a missing method would otherwise surface as a runtime TypeError in a
- * callback that needs a real dev store to reach.
- *
- * @param {any} storage
- * @returns {SessionStorage}
- */
-const ensureStorage = (storage) => {
-    const missing = (0, index_js_1.ensureArray)(exports.STORAGE_METHODS).filter((method) => (typeof (storage === null || storage === void 0 ? void 0 : storage[method]) !== 'function'));
-    if (missing.length) {
-        throw new Error(`Invalid session storage, missing: ${missing.join(', ')}`);
-    }
-    return storage;
-};
-exports.ensureStorage = ensureStorage;