@palbase/backend 10.2.0 → 11.0.0

package/dist/purchases/keys.cjs

@@ -0,0 +1,19 @@
+"use strict";
+var __defProp = Object.defineProperty;
+var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
+var __getOwnPropNames = Object.getOwnPropertyNames;
+var __hasOwnProp = Object.prototype.hasOwnProperty;
+var __copyProps = (to, from, except, desc) => {
+  if (from && typeof from === "object" || typeof from === "function") {
+    for (let key of __getOwnPropNames(from))
+      if (!__hasOwnProp.call(to, key) && key !== except)
+        __defProp(to, key, { get: () => from[key], enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable });
+  }
+  return to;
+};
+var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: true }), mod);
+
+// src/purchases/keys.ts
+var keys_exports = {};
+module.exports = __toCommonJS(keys_exports);
+//# sourceMappingURL=keys.cjs.map

package/dist/purchases/keys.cjs.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/purchases/keys.ts"],"sourcesContent":["/**\n * `@palbase/backend/purchases` — the controlled global augmentation target for\n * the project's purchases catalog.\n *\n * `@RequireEntitlement(...)` and `@Spend(...)` take these unions, never a raw\n * string, so a typo is a COMPILE error rather than a 500 in production or —\n * worse — a spend against a limit key that silently does not exist. This is the\n * TypeScript half of what swiftgen already does for iOS: one catalog, two\n * languages, neither of them hand-maintained.\n *\n * Both interfaces are EMPTY by default; the generated `palbase-purchases.d.ts`\n * augments them with one member per catalog entry:\n *\n *   // palbase-purchases.d.ts (generated — do not edit)\n *   declare module \"@palbase/backend/purchases\" {\n *     interface Entitlements { pro: true }\n *     interface Limits { bookCreate: true }\n *   }\n *\n * A project with no catalog therefore has NO valid keys, and every decorator\n * call fails to compile until its catalog is generated. That is the intended\n * behaviour, not a rough edge: it is the same single-project augmentation model\n * `@palbase/backend/env` uses for `Database.tables`.\n */\n\n/**\n * The project's entitlement keys. EMPTY by default; filled by the generated\n * `palbase-purchases.d.ts`.\n */\n// biome-ignore lint/suspicious/noEmptyInterface: augmentation target — filled by generated palbase-purchases.d.ts.\nexport interface Entitlements {}\n\n/**\n * The project's limit and credit keys — everything `@Spend` can consume. EMPTY\n * by default; filled by the generated `palbase-purchases.d.ts`.\n */\n// biome-ignore lint/suspicious/noEmptyInterface: augmentation target — filled by generated palbase-purchases.d.ts.\nexport interface Limits {}\n\n/** Every entitlement key the project's catalog declares. */\nexport type EntitlementKey = keyof Entitlements & string;\n\n/** Every limit/credit key the project's catalog declares. */\nexport type LimitKey = keyof Limits & string;\n"],"mappings":";;;;;;;;;;;;;;;;AAAA;AAAA;","names":[]}

package/dist/purchases/keys.d.cts

@@ -0,0 +1,42 @@
+/**
+ * `@palbase/backend/purchases` — the controlled global augmentation target for
+ * the project's purchases catalog.
+ *
+ * `@RequireEntitlement(...)` and `@Spend(...)` take these unions, never a raw
+ * string, so a typo is a COMPILE error rather than a 500 in production or —
+ * worse — a spend against a limit key that silently does not exist. This is the
+ * TypeScript half of what swiftgen already does for iOS: one catalog, two
+ * languages, neither of them hand-maintained.
+ *
+ * Both interfaces are EMPTY by default; the generated `palbase-purchases.d.ts`
+ * augments them with one member per catalog entry:
+ *
+ *   // palbase-purchases.d.ts (generated — do not edit)
+ *   declare module "@palbase/backend/purchases" {
+ *     interface Entitlements { pro: true }
+ *     interface Limits { bookCreate: true }
+ *   }
+ *
+ * A project with no catalog therefore has NO valid keys, and every decorator
+ * call fails to compile until its catalog is generated. That is the intended
+ * behaviour, not a rough edge: it is the same single-project augmentation model
+ * `@palbase/backend/env` uses for `Database.tables`.
+ */
+/**
+ * The project's entitlement keys. EMPTY by default; filled by the generated
+ * `palbase-purchases.d.ts`.
+ */
+interface Entitlements {
+}
+/**
+ * The project's limit and credit keys — everything `@Spend` can consume. EMPTY
+ * by default; filled by the generated `palbase-purchases.d.ts`.
+ */
+interface Limits {
+}
+/** Every entitlement key the project's catalog declares. */
+type EntitlementKey = keyof Entitlements & string;
+/** Every limit/credit key the project's catalog declares. */
+type LimitKey = keyof Limits & string;
+
+export type { EntitlementKey, Entitlements, LimitKey, Limits };

package/dist/purchases/keys.d.ts

@@ -0,0 +1,42 @@
+/**
+ * `@palbase/backend/purchases` — the controlled global augmentation target for
+ * the project's purchases catalog.
+ *
+ * `@RequireEntitlement(...)` and `@Spend(...)` take these unions, never a raw
+ * string, so a typo is a COMPILE error rather than a 500 in production or —
+ * worse — a spend against a limit key that silently does not exist. This is the
+ * TypeScript half of what swiftgen already does for iOS: one catalog, two
+ * languages, neither of them hand-maintained.
+ *
+ * Both interfaces are EMPTY by default; the generated `palbase-purchases.d.ts`
+ * augments them with one member per catalog entry:
+ *
+ *   // palbase-purchases.d.ts (generated — do not edit)
+ *   declare module "@palbase/backend/purchases" {
+ *     interface Entitlements { pro: true }
+ *     interface Limits { bookCreate: true }
+ *   }
+ *
+ * A project with no catalog therefore has NO valid keys, and every decorator
+ * call fails to compile until its catalog is generated. That is the intended
+ * behaviour, not a rough edge: it is the same single-project augmentation model
+ * `@palbase/backend/env` uses for `Database.tables`.
+ */
+/**
+ * The project's entitlement keys. EMPTY by default; filled by the generated
+ * `palbase-purchases.d.ts`.
+ */
+interface Entitlements {
+}
+/**
+ * The project's limit and credit keys — everything `@Spend` can consume. EMPTY
+ * by default; filled by the generated `palbase-purchases.d.ts`.
+ */
+interface Limits {
+}
+/** Every entitlement key the project's catalog declares. */
+type EntitlementKey = keyof Entitlements & string;
+/** Every limit/credit key the project's catalog declares. */
+type LimitKey = keyof Limits & string;
+
+export type { EntitlementKey, Entitlements, LimitKey, Limits };

package/dist/purchases/keys.js

@@ -0,0 +1 @@
+//# sourceMappingURL=keys.js.map

package/dist/purchases/keys.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":[],"sourcesContent":[],"mappings":"","names":[]}