@wildo-ai/saas-website 1.1.3 → 1.1.5

package/dist/esm/schemas/label-keys/website-consent-label-keys.schemas.d.ts

@@ -0,0 +1,61 @@
+import { ConsentPurpose } from '@wildo-ai/saas-models/public-runtime';
+import { type WebsiteLabelKey } from './website-label-key.schemas';
+/**
+ * The label keys the framework's visitor consent surface reads (#534).
+ *
+ * FRAMEWORK-OWNED, like the skip link's key: the consent banner is rendered by `WebsitePageLayout`, not by
+ * the site's chrome, so the site does not list these in `chromeLabelKeys`.
+ * `composeEffectiveChromeLabelKeys` unions them into the label-pack validator's expected set, so a locale
+ * pack missing one fails the build rather than showing a visitor a raw key.
+ *
+ * They are required of every site, including one that runs no consent-based provider today: the words are
+ * cheap, and a site that adds analytics tomorrow must not ship it with an unlabelled — or absent — way to
+ * refuse.
+ *
+ * Purpose names are keyed by the `ConsentPurpose` VALUE and derived from the vocabulary, so a purpose added
+ * to it is a missing label in every site's pack at the next build, not a purpose the banner cannot name.
+ */
+export declare enum WebsiteConsentLabelSlot {
+    /** Heading of the consent panel. */
+    TITLE = "title",
+    /** What the panel is for: optional purposes are off until agreed, each chosen separately, changeable later. */
+    DESCRIPTION = "description",
+    /** Agree to every purpose listed. */
+    ACCEPT_ALL = "accept-all",
+    /** Agree to none of them — recorded as a choice, so the panel does not return. */
+    DECLINE_ALL = "decline-all",
+    /** Save exactly the purposes ticked. */
+    SAVE = "save",
+    /** Re-open the panel to change a choice already made. */
+    MANAGE = "manage",
+    /**
+     * Name of the row covering what runs whatever the visitor chooses.
+     *
+     * NOT a `ConsentPurpose`, and it must never become one: that vocabulary is what a visitor DECIDES,
+     * and this is the thing they are not being asked about. It is shown because a panel listing only
+     * the optional purposes cannot answer the question a visitor opened it to answer — what is
+     * happening on this site — which is why every specialized consent platform states it.
+     */
+    ESSENTIAL_TITLE = "essential-title",
+    /** What the always-active row covers, and why its control is checked and cannot be changed. */
+    ESSENTIAL_DESCRIPTION = "essential-description"
+}
+/** The fully-composed key for one panel slot. */
+export declare function websiteConsentLabelKey(slot: WebsiteConsentLabelSlot): WebsiteLabelKey;
+/** The fully-composed key naming one consent purpose. */
+export declare function websiteConsentPurposeLabelKey(purpose: ConsentPurpose): WebsiteLabelKey;
+/**
+ * The key EXPLAINING one consent purpose — what agreeing to it means for this visitor.
+ *
+ * The name above answers *what is it called*; this answers *what will happen to me*, and a choice
+ * made without the second is not an informed one. "Analytics" beside a tick box is a category, not
+ * something a visitor can weigh.
+ *
+ * Derived from the vocabulary exactly as the name is, so a purpose added to `ConsentPurpose` is a
+ * missing label in every site's pack at the next build rather than a row that renders a name with no
+ * explanation beneath it.
+ */
+export declare function websiteConsentPurposeDescriptionLabelKey(purpose: ConsentPurpose): WebsiteLabelKey;
+/** Every framework-owned consent key — what a locale pack must carry. Total over both vocabularies. */
+export declare const WEBSITE_CONSENT_LABEL_KEYS: readonly WebsiteLabelKey[];
+//# sourceMappingURL=website-consent-label-keys.schemas.d.ts.map

package/dist/esm/schemas/label-keys/website-consent-label-keys.schemas.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"website-consent-label-keys.schemas.d.ts","sourceRoot":"","sources":["../../../../../src/schemas/label-keys/website-consent-label-keys.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,cAAc,EAAoB,MAAM,sCAAsC,CAAC;AAExF,OAAO,EAAyB,KAAK,eAAe,EAAE,MAAM,6BAA6B,CAAC;AAE1F;;;;;;;;;;;;;;GAcG;AACH,oBAAY,uBAAuB;IACjC,oCAAoC;IACpC,KAAK,UAAU;IACf,+GAA+G;IAC/G,WAAW,gBAAgB;IAC3B,qCAAqC;IACrC,UAAU,eAAe;IACzB,kFAAkF;IAClF,WAAW,gBAAgB;IAC3B,wCAAwC;IACxC,IAAI,SAAS;IACb,yDAAyD;IACzD,MAAM,WAAW;IACjB;;;;;;;OAOG;IACH,eAAe,oBAAoB;IACnC,+FAA+F;IAC/F,qBAAqB,0BAA0B;CAChD;AAID,iDAAiD;AACjD,wBAAgB,sBAAsB,CAAC,IAAI,EAAE,uBAAuB,GAAG,eAAe,CAErF;AAED,yDAAyD;AACzD,wBAAgB,6BAA6B,CAAC,OAAO,EAAE,cAAc,GAAG,eAAe,CAEtF;AAED;;;;;;;;;;GAUG;AACH,wBAAgB,wCAAwC,CAAC,OAAO,EAAE,cAAc,GAAG,eAAe,CAEjG;AAED,uGAAuG;AACvG,eAAO,MAAM,0BAA0B,EAAE,SAAS,eAAe,EAI/D,CAAC"}

package/dist/esm/schemas/label-keys/website-consent-label-keys.schemas.js

@@ -0,0 +1,73 @@
+import { CONSENT_PURPOSES } from '@wildo-ai/saas-models/public-runtime';
+import { WebsiteLabelKeySchema } from './website-label-key.schemas.js';
+/**
+ * The label keys the framework's visitor consent surface reads (#534).
+ *
+ * FRAMEWORK-OWNED, like the skip link's key: the consent banner is rendered by `WebsitePageLayout`, not by
+ * the site's chrome, so the site does not list these in `chromeLabelKeys`.
+ * `composeEffectiveChromeLabelKeys` unions them into the label-pack validator's expected set, so a locale
+ * pack missing one fails the build rather than showing a visitor a raw key.
+ *
+ * They are required of every site, including one that runs no consent-based provider today: the words are
+ * cheap, and a site that adds analytics tomorrow must not ship it with an unlabelled — or absent — way to
+ * refuse.
+ *
+ * Purpose names are keyed by the `ConsentPurpose` VALUE and derived from the vocabulary, so a purpose added
+ * to it is a missing label in every site's pack at the next build, not a purpose the banner cannot name.
+ */
+export var WebsiteConsentLabelSlot;
+(function (WebsiteConsentLabelSlot) {
+    /** Heading of the consent panel. */
+    WebsiteConsentLabelSlot["TITLE"] = "title";
+    /** What the panel is for: optional purposes are off until agreed, each chosen separately, changeable later. */
+    WebsiteConsentLabelSlot["DESCRIPTION"] = "description";
+    /** Agree to every purpose listed. */
+    WebsiteConsentLabelSlot["ACCEPT_ALL"] = "accept-all";
+    /** Agree to none of them — recorded as a choice, so the panel does not return. */
+    WebsiteConsentLabelSlot["DECLINE_ALL"] = "decline-all";
+    /** Save exactly the purposes ticked. */
+    WebsiteConsentLabelSlot["SAVE"] = "save";
+    /** Re-open the panel to change a choice already made. */
+    WebsiteConsentLabelSlot["MANAGE"] = "manage";
+    /**
+     * Name of the row covering what runs whatever the visitor chooses.
+     *
+     * NOT a `ConsentPurpose`, and it must never become one: that vocabulary is what a visitor DECIDES,
+     * and this is the thing they are not being asked about. It is shown because a panel listing only
+     * the optional purposes cannot answer the question a visitor opened it to answer — what is
+     * happening on this site — which is why every specialized consent platform states it.
+     */
+    WebsiteConsentLabelSlot["ESSENTIAL_TITLE"] = "essential-title";
+    /** What the always-active row covers, and why its control is checked and cannot be changed. */
+    WebsiteConsentLabelSlot["ESSENTIAL_DESCRIPTION"] = "essential-description";
+})(WebsiteConsentLabelSlot || (WebsiteConsentLabelSlot = {}));
+const CONSENT_LABEL_KEY_PREFIX = 'website.chrome.consent';
+/** The fully-composed key for one panel slot. */
+export function websiteConsentLabelKey(slot) {
+    return WebsiteLabelKeySchema.parse(`${CONSENT_LABEL_KEY_PREFIX}.${slot}`);
+}
+/** The fully-composed key naming one consent purpose. */
+export function websiteConsentPurposeLabelKey(purpose) {
+    return WebsiteLabelKeySchema.parse(`${CONSENT_LABEL_KEY_PREFIX}.purpose-${purpose}`);
+}
+/**
+ * The key EXPLAINING one consent purpose — what agreeing to it means for this visitor.
+ *
+ * The name above answers *what is it called*; this answers *what will happen to me*, and a choice
+ * made without the second is not an informed one. "Analytics" beside a tick box is a category, not
+ * something a visitor can weigh.
+ *
+ * Derived from the vocabulary exactly as the name is, so a purpose added to `ConsentPurpose` is a
+ * missing label in every site's pack at the next build rather than a row that renders a name with no
+ * explanation beneath it.
+ */
+export function websiteConsentPurposeDescriptionLabelKey(purpose) {
+    return WebsiteLabelKeySchema.parse(`${CONSENT_LABEL_KEY_PREFIX}.purpose-${purpose}-description`);
+}
+/** Every framework-owned consent key — what a locale pack must carry. Total over both vocabularies. */
+export const WEBSITE_CONSENT_LABEL_KEYS = Object.freeze([
+    ...Object.values(WebsiteConsentLabelSlot).map(websiteConsentLabelKey),
+    ...CONSENT_PURPOSES.map(websiteConsentPurposeLabelKey),
+    ...CONSENT_PURPOSES.map(websiteConsentPurposeDescriptionLabelKey),
+]);
+//# sourceMappingURL=website-consent-label-keys.schemas.js.map

package/dist/esm/schemas/label-keys/website-consent-label-keys.schemas.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"website-consent-label-keys.schemas.js","sourceRoot":"","sources":["../../../../../src/schemas/label-keys/website-consent-label-keys.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAkB,gBAAgB,EAAE,MAAM,sCAAsC,CAAC;AAExF,OAAO,EAAE,qBAAqB,EAAwB,MAAM,6BAA6B,CAAC;AAE1F;;;;;;;;;;;;;;GAcG;AACH,MAAM,CAAN,IAAY,uBAwBX;AAxBD,WAAY,uBAAuB;IACjC,oCAAoC;IACpC,0CAAe,CAAA;IACf,+GAA+G;IAC/G,sDAA2B,CAAA;IAC3B,qCAAqC;IACrC,oDAAyB,CAAA;IACzB,kFAAkF;IAClF,sDAA2B,CAAA;IAC3B,wCAAwC;IACxC,wCAAa,CAAA;IACb,yDAAyD;IACzD,4CAAiB,CAAA;IACjB;;;;;;;OAOG;IACH,8DAAmC,CAAA;IACnC,+FAA+F;IAC/F,0EAA+C,CAAA;AACjD,CAAC,EAxBW,uBAAuB,KAAvB,uBAAuB,QAwBlC;AAED,MAAM,wBAAwB,GAAG,wBAAwB,CAAC;AAE1D,iDAAiD;AACjD,MAAM,UAAU,sBAAsB,CAAC,IAA6B;IAClE,OAAO,qBAAqB,CAAC,KAAK,CAAC,GAAG,wBAAwB,IAAI,IAAI,EAAE,CAAC,CAAC;AAC5E,CAAC;AAED,yDAAyD;AACzD,MAAM,UAAU,6BAA6B,CAAC,OAAuB;IACnE,OAAO,qBAAqB,CAAC,KAAK,CAAC,GAAG,wBAAwB,YAAY,OAAO,EAAE,CAAC,CAAC;AACvF,CAAC;AAED;;;;;;;;;;GAUG;AACH,MAAM,UAAU,wCAAwC,CAAC,OAAuB;IAC9E,OAAO,qBAAqB,CAAC,KAAK,CAAC,GAAG,wBAAwB,YAAY,OAAO,cAAc,CAAC,CAAC;AACnG,CAAC;AAED,uGAAuG;AACvG,MAAM,CAAC,MAAM,0BAA0B,GAA+B,MAAM,CAAC,MAAM,CAAC;IAClF,GAAG,MAAM,CAAC,MAAM,CAAC,uBAAuB,CAAC,CAAC,GAAG,CAAC,sBAAsB,CAAC;IACrE,GAAG,gBAAgB,CAAC,GAAG,CAAC,6BAA6B,CAAC;IACtD,GAAG,gBAAgB,CAAC,GAAG,CAAC,wCAAwC,CAAC;CAClE,CAAC,CAAC","sourcesContent":["import { ConsentPurpose, CONSENT_PURPOSES } from '@wildo-ai/saas-models/public-runtime';\n\nimport { WebsiteLabelKeySchema, type WebsiteLabelKey } from './website-label-key.schemas';\n\n/**\n * The label keys the framework's visitor consent surface reads (#534).\n *\n * FRAMEWORK-OWNED, like the skip link's key: the consent banner is rendered by `WebsitePageLayout`, not by\n * the site's chrome, so the site does not list these in `chromeLabelKeys`.\n * `composeEffectiveChromeLabelKeys` unions them into the label-pack validator's expected set, so a locale\n * pack missing one fails the build rather than showing a visitor a raw key.\n *\n * They are required of every site, including one that runs no consent-based provider today: the words are\n * cheap, and a site that adds analytics tomorrow must not ship it with an unlabelled — or absent — way to\n * refuse.\n *\n * Purpose names are keyed by the `ConsentPurpose` VALUE and derived from the vocabulary, so a purpose added\n * to it is a missing label in every site's pack at the next build, not a purpose the banner cannot name.\n */\nexport enum WebsiteConsentLabelSlot {\n  /** Heading of the consent panel. */\n  TITLE = 'title',\n  /** What the panel is for: optional purposes are off until agreed, each chosen separately, changeable later. */\n  DESCRIPTION = 'description',\n  /** Agree to every purpose listed. */\n  ACCEPT_ALL = 'accept-all',\n  /** Agree to none of them — recorded as a choice, so the panel does not return. */\n  DECLINE_ALL = 'decline-all',\n  /** Save exactly the purposes ticked. */\n  SAVE = 'save',\n  /** Re-open the panel to change a choice already made. */\n  MANAGE = 'manage',\n  /**\n   * Name of the row covering what runs whatever the visitor chooses.\n   *\n   * NOT a `ConsentPurpose`, and it must never become one: that vocabulary is what a visitor DECIDES,\n   * and this is the thing they are not being asked about. It is shown because a panel listing only\n   * the optional purposes cannot answer the question a visitor opened it to answer — what is\n   * happening on this site — which is why every specialized consent platform states it.\n   */\n  ESSENTIAL_TITLE = 'essential-title',\n  /** What the always-active row covers, and why its control is checked and cannot be changed. */\n  ESSENTIAL_DESCRIPTION = 'essential-description',\n}\n\nconst CONSENT_LABEL_KEY_PREFIX = 'website.chrome.consent';\n\n/** The fully-composed key for one panel slot. */\nexport function websiteConsentLabelKey(slot: WebsiteConsentLabelSlot): WebsiteLabelKey {\n  return WebsiteLabelKeySchema.parse(`${CONSENT_LABEL_KEY_PREFIX}.${slot}`);\n}\n\n/** The fully-composed key naming one consent purpose. */\nexport function websiteConsentPurposeLabelKey(purpose: ConsentPurpose): WebsiteLabelKey {\n  return WebsiteLabelKeySchema.parse(`${CONSENT_LABEL_KEY_PREFIX}.purpose-${purpose}`);\n}\n\n/**\n * The key EXPLAINING one consent purpose — what agreeing to it means for this visitor.\n *\n * The name above answers *what is it called*; this answers *what will happen to me*, and a choice\n * made without the second is not an informed one. \"Analytics\" beside a tick box is a category, not\n * something a visitor can weigh.\n *\n * Derived from the vocabulary exactly as the name is, so a purpose added to `ConsentPurpose` is a\n * missing label in every site's pack at the next build rather than a row that renders a name with no\n * explanation beneath it.\n */\nexport function websiteConsentPurposeDescriptionLabelKey(purpose: ConsentPurpose): WebsiteLabelKey {\n  return WebsiteLabelKeySchema.parse(`${CONSENT_LABEL_KEY_PREFIX}.purpose-${purpose}-description`);\n}\n\n/** Every framework-owned consent key — what a locale pack must carry. Total over both vocabularies. */\nexport const WEBSITE_CONSENT_LABEL_KEYS: readonly WebsiteLabelKey[] = Object.freeze([\n  ...Object.values(WebsiteConsentLabelSlot).map(websiteConsentLabelKey),\n  ...CONSENT_PURPOSES.map(websiteConsentPurposeLabelKey),\n  ...CONSENT_PURPOSES.map(websiteConsentPurposeDescriptionLabelKey),\n]);\n"]}