@redacto.io/consent-sdk-react 10.0.0-beta.11 → 10.0.0-beta.12

package/dist/types-6Aj7faxL.d.mts

@@ -0,0 +1,57 @@
+/**
+ * Types shared by the three notice components (RedactoNoticeConsent,
+ * RedactoNoticeConsentInline, RedactoNoticeAssisted).
+ */
+/** Output format published for each webfont weight. */
+type NoticeFontFormat = "woff2" | "ttf";
+/** Generic CSS family a font falls back to; native platforms map it to their own default. */
+type NoticeFontGenericFallback = "sans-serif" | "serif" | "monospace";
+type NoticeFontEntryBase = {
+    /** Lower-cased match key; equals `value.toLowerCase()`. */
+    id: string;
+    /** CDN directory and DOM id segment. */
+    slug: string;
+    /** Exact string stored in the notice's `font_preference`. */
+    value: string;
+    /** Label shown in the console dropdown. */
+    label: string;
+    /** Family name used in `@font-face` and `local()`. */
+    cssFamily: string;
+    /** Full CSS `font-family` value the notice emits. */
+    stack: string;
+    genericFallback: NoticeFontGenericFallback;
+};
+/** A family already present on the device — referenced by name, never fetched. */
+type NoticeSystemFont = NoticeFontEntryBase & {
+    source: "system";
+};
+/**
+ * A family that does not ship with the operating system. Its files are bundled
+ * inside this package for web, and published to the CDN for the native SDKs,
+ * which cannot bundle from an npm package.
+ */
+type NoticeWebFont = NoticeFontEntryBase & {
+    source: "webfont";
+    /** Per-family: not every family publishes all four notice weights. */
+    weights: ReadonlyArray<number>;
+    formats: ReadonlyArray<NoticeFontFormat>;
+};
+type NoticeFontEntry = NoticeSystemFont | NoticeWebFont;
+/** Host-level webfont configuration, applied via `configureNoticeFonts`. */
+type NoticeFontOptions = {
+    /**
+     * Skip webfont loading entirely; families resolve to their fallback stack,
+     * which is a same-genre face. Useful to avoid the per-family payload, or when
+     * a strict CSP omits `data:` from `font-src`.
+     */
+    disabled?: boolean;
+};
+/** Ordered font candidates for a notice: the host's override, then the notice config. */
+type NoticeFontSourceValue = {
+    /** Host-supplied `settings.font`; wins when set. */
+    hostFont?: string;
+    /** The notice config's `font_preference`. */
+    noticeFont?: string;
+};
+
+export type { NoticeFontEntry as N, NoticeFontSourceValue as a, NoticeFontFormat as b, NoticeFontGenericFallback as c, NoticeSystemFont as d, NoticeWebFont as e, NoticeFontOptions as f };

package/dist/types-6Aj7faxL.d.ts

@@ -0,0 +1,57 @@
+/**
+ * Types shared by the three notice components (RedactoNoticeConsent,
+ * RedactoNoticeConsentInline, RedactoNoticeAssisted).
+ */
+/** Output format published for each webfont weight. */
+type NoticeFontFormat = "woff2" | "ttf";
+/** Generic CSS family a font falls back to; native platforms map it to their own default. */
+type NoticeFontGenericFallback = "sans-serif" | "serif" | "monospace";
+type NoticeFontEntryBase = {
+    /** Lower-cased match key; equals `value.toLowerCase()`. */
+    id: string;
+    /** CDN directory and DOM id segment. */
+    slug: string;
+    /** Exact string stored in the notice's `font_preference`. */
+    value: string;
+    /** Label shown in the console dropdown. */
+    label: string;
+    /** Family name used in `@font-face` and `local()`. */
+    cssFamily: string;
+    /** Full CSS `font-family` value the notice emits. */
+    stack: string;
+    genericFallback: NoticeFontGenericFallback;
+};
+/** A family already present on the device — referenced by name, never fetched. */
+type NoticeSystemFont = NoticeFontEntryBase & {
+    source: "system";
+};
+/**
+ * A family that does not ship with the operating system. Its files are bundled
+ * inside this package for web, and published to the CDN for the native SDKs,
+ * which cannot bundle from an npm package.
+ */
+type NoticeWebFont = NoticeFontEntryBase & {
+    source: "webfont";
+    /** Per-family: not every family publishes all four notice weights. */
+    weights: ReadonlyArray<number>;
+    formats: ReadonlyArray<NoticeFontFormat>;
+};
+type NoticeFontEntry = NoticeSystemFont | NoticeWebFont;
+/** Host-level webfont configuration, applied via `configureNoticeFonts`. */
+type NoticeFontOptions = {
+    /**
+     * Skip webfont loading entirely; families resolve to their fallback stack,
+     * which is a same-genre face. Useful to avoid the per-family payload, or when
+     * a strict CSP omits `data:` from `font-src`.
+     */
+    disabled?: boolean;
+};
+/** Ordered font candidates for a notice: the host's override, then the notice config. */
+type NoticeFontSourceValue = {
+    /** Host-supplied `settings.font`; wins when set. */
+    hostFont?: string;
+    /** The notice config's `font_preference`. */
+    noticeFont?: string;
+};
+
+export type { NoticeFontEntry as N, NoticeFontSourceValue as a, NoticeFontFormat as b, NoticeFontGenericFallback as c, NoticeSystemFont as d, NoticeWebFont as e, NoticeFontOptions as f };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@redacto.io/consent-sdk-react",
-  "version": "10.0.0-beta.11",
+  "version": "10.0.0-beta.12",
   "main": "dist/index.cjs",
   "module": "dist/index.mjs",
   "types": "dist/index.d.ts",
@@ -14,8 +14,17 @@
       "types": "./dist/privacy-center.d.ts",
       "require": "./dist/privacy-center.cjs",
       "import": "./dist/privacy-center.mjs"
+    },
+    "./fonts": {
+      "types": "./dist/fonts.d.ts",
+      "require": "./dist/fonts.js",
+      "import": "./dist/fonts.mjs"
     }
   },
+  "files": [
+    "dist",
+    "NOTICE.md"
+  ],
   "keywords": [],
   "author": "",
   "license": "Apache-2.0",

package/.turbo/turbo-build.log

@@ -1,22 +0,0 @@
-$ tsup
-CLI Building entry: {"index":"src/index.ts","privacy-center":"src/privacy-center.ts"}
-CLI Using tsconfig: tsconfig.json
-CLI tsup v8.5.1
-CLI Using tsup config: /Users/sadanmianredacto/Developer/redacto/consent-sdk/packages/consent-sdk-react/tsup.config.ts
-CLI Target: es2019
-CLI Cleaning output folder
-ESM Build start
-CJS Build start
-CJS dist/index.js          516.41 KB
-CJS dist/privacy-center.js 2.21 MB
-CJS ⚡️ Build success in 179ms
-ESM dist/chunk-6A665OPR.mjs 841.00 B
-ESM dist/index.mjs          501.90 KB
-ESM dist/privacy-center.mjs 2.17 MB
-ESM ⚡️ Build success in 184ms
-DTS Build start
-DTS ⚡️ Build success in 3448ms
-DTS dist/index.d.mts          8.42 KB
-DTS dist/privacy-center.d.mts 33.31 KB
-DTS dist/index.d.ts           8.42 KB
-DTS dist/privacy-center.d.ts  33.31 KB

package/.turbo/turbo-test.log

@@ -1,203 +0,0 @@
-
-> @redacto.io/consent-sdk-react@9.2.0 test /Users/sadanmianredacto/Developer/redacto/consent-sdk/packages/consent-sdk-react
-> vitest run
-
-
- RUN  v4.1.8 /Users/sadanmianredacto/Developer/redacto/consent-sdk/packages/consent-sdk-react
-
- ✓ tests/DataAvailabilityContext.test.tsx (7 tests) 32ms
-stderr | src/RedactoNoticeConsentInline/RedactoNoticeConsentInline.test.tsx > RedactoConsentInline > renders loading state initially
-An update to RedactoConsentInline inside a test was not wrapped in act(...).
-
-When testing, code that causes React state updates should be wrapped into act(...):
-
-act(() => {
-  /* fire events that update state */
-});
-/* assert on the output */
-
-This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
-An update to RedactoConsentInline inside a test was not wrapped in act(...).
-
-When testing, code that causes React state updates should be wrapped into act(...):
-
-act(() => {
-  /* fire events that update state */
-});
-/* assert on the output */
-
-This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
-An update to RedactoConsentInline inside a test was not wrapped in act(...).
-
-When testing, code that causes React state updates should be wrapped into act(...):
-
-act(() => {
-  /* fire events that update state */
-});
-/* assert on the output */
-
-This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
-An update to RedactoConsentInline inside a test was not wrapped in act(...).
-
-When testing, code that causes React state updates should be wrapped into act(...):
-
-act(() => {
-  /* fire events that update state */
-});
-/* assert on the output */
-
-This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
-An update to RedactoConsentInline inside a test was not wrapped in act(...).
-
-When testing, code that causes React state updates should be wrapped into act(...):
-
-act(() => {
-  /* fire events that update state */
-});
-/* assert on the output */
-
-This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
-An update to RedactoConsentInline inside a test was not wrapped in act(...).
-
-When testing, code that causes React state updates should be wrapped into act(...):
-
-act(() => {
-  /* fire events that update state */
-});
-/* assert on the output */
-
-This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
-
-stderr | src/RedactoNoticeConsent/RedactoNoticeConsent.test.tsx > RedactoNoticeConsent > renders loading state initially
-An update to RedactoNoticeConsent inside a test was not wrapped in act(...).
-
-When testing, code that causes React state updates should be wrapped into act(...):
-
-act(() => {
-  /* fire events that update state */
-});
-/* assert on the output */
-
-This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
-An update to RedactoNoticeConsent inside a test was not wrapped in act(...).
-
-When testing, code that causes React state updates should be wrapped into act(...):
-
-act(() => {
-  /* fire events that update state */
-});
-/* assert on the output */
-
-This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
-An update to RedactoNoticeConsent inside a test was not wrapped in act(...).
-
-When testing, code that causes React state updates should be wrapped into act(...):
-
-act(() => {
-  /* fire events that update state */
-});
-/* assert on the output */
-
-This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
-An update to RedactoNoticeConsent inside a test was not wrapped in act(...).
-
-When testing, code that causes React state updates should be wrapped into act(...):
-
-act(() => {
-  /* fire events that update state */
-});
-/* assert on the output */
-
-This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
-An update to RedactoNoticeConsent inside a test was not wrapped in act(...).
-
-When testing, code that causes React state updates should be wrapped into act(...):
-
-act(() => {
-  /* fire events that update state */
-});
-/* assert on the output */
-
-This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
-An update to RedactoNoticeConsent inside a test was not wrapped in act(...).
-
-When testing, code that causes React state updates should be wrapped into act(...):
-
-act(() => {
-  /* fire events that update state */
-});
-/* assert on the output */
-
-This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
-An update to RedactoNoticeConsent inside a test was not wrapped in act(...).
-
-When testing, code that causes React state updates should be wrapped into act(...):
-
-act(() => {
-  /* fire events that update state */
-});
-/* assert on the output */
-
-This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
-An update to RedactoNoticeConsent inside a test was not wrapped in act(...).
-
-When testing, code that causes React state updates should be wrapped into act(...):
-
-act(() => {
-  /* fire events that update state */
-});
-/* assert on the output */
-
-This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
-An update to RedactoNoticeConsent inside a test was not wrapped in act(...).
-
-When testing, code that causes React state updates should be wrapped into act(...):
-
-act(() => {
-  /* fire events that update state */
-});
-/* assert on the output */
-
-This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
-
- ✓ tests/ProductSelectionSection.test.tsx (10 tests) 46ms
- ✓ tests/RequestSubmit.test.tsx (5 tests) 50ms
-stderr | tests/Form.test.tsx > Form (P2-SDK-3) > blocks submit for product-scoped types when the DP has no consent groups
-No purposes with data elements found in API response
-
- ✓ src/RedactoNoticeConsentInline/RedactoNoticeConsentInline.test.tsx (14 tests) 150ms
-stderr | tests/Form.test.tsx > Form (P2-SDK-3) > renders the product step for DSAR types when direct_groups is present
-No purposes with data elements found in API response
-
-stderr | tests/Form.test.tsx > Form (P2-SDK-3) > skips the product selection step when only one consent group exists
-No purposes with data elements found in API response
-
-stderr | tests/Form.test.tsx > Form (P2-SDK-3) > skips the product step for nomination and grievance
-No purposes with data elements found in API response
-
-stderr | tests/Form.test.tsx > Form (P2-SDK-3) > fires one createCaseRequest with correct anchors on single-product erasure submit
-No purposes with data elements found in API response
-
-stderr | tests/Form.test.tsx > Form (P2-SDK-3) > switches the inline purpose panel when another product chip is selected
-No purposes with data elements found in API response
-
-stderr | tests/Form.test.tsx > Form (P2-SDK-3) > disambiguates direct vs nominated chips on the same product via inline panel header
-No purposes with data elements found in API response
-
-stderr | tests/Form.test.tsx > Form (P2-SDK-3) > submits NOMINATION as an org-level case without product_uuid or data_principal_uuid
-No purposes with data elements found in API response
-
-stderr | tests/Form.test.tsx > Form (P2-SDK-3) > sends data_principal_uuid and product anchors on a nominated-card submit
-No purposes with data elements found in API response
-
-stderr | tests/Form.test.tsx > Form (P2-SDK-3) > disables submit when the selected CORRECTION product has incomplete entries
-No purposes with data elements found in API response
-
- ✓ tests/Form.test.tsx (11 tests) 280ms
- ✓ src/RedactoNoticeConsent/RedactoNoticeConsent.test.tsx (31 tests) 408ms
-
- Test Files  6 passed (6)
-      Tests  78 passed (78)
-   Start at  03:16:13
-   Duration  1.08s (transform 953ms, setup 358ms, import 1.63s, tests 966ms, environment 1.58s)
-

package/.turbo/turbo-verify-pack.log

@@ -1,6 +0,0 @@
-
-> @redacto.io/consent-sdk-react@9.2.0 verify-pack /Users/sadanmianredacto/Developer/redacto/consent-sdk/packages/consent-sdk-react
-> node ../../scripts/verify-pack.mjs .
-
-verify-pack: @redacto.io/consent-sdk-react@9.2.0 — 12 packed files
-verify-pack: @redacto.io/consent-sdk-react OK