@redacto.io/consent-sdk-react 10.0.0-beta.1 → 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.1",
+  "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          520.79 KB
-CJS dist/privacy-center.js 2.24 MB
-CJS ⚡️ Build success in 124ms
-ESM dist/index.mjs          506.34 KB
-ESM dist/chunk-6A665OPR.mjs 841.00 B
-ESM dist/privacy-center.mjs 2.20 MB
-ESM ⚡️ Build success in 124ms
-DTS Build start
-DTS ⚡️ Build success in 2664ms
-DTS dist/index.d.mts          8.27 KB
-DTS dist/privacy-center.d.mts 33.25 KB
-DTS dist/index.d.ts           8.27 KB
-DTS dist/privacy-center.d.ts  33.25 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

package/CHANGELOG.md

@@ -1,274 +0,0 @@
-# @redacto.io/consent-sdk-react
-
-## 10.0.0-beta.1
-
-### Major Changes
-
-- feat(privacy-center): shared-contact profile picker (OTP + embeddable SDK)
-
-### Minor Changes
-
-- 61d18e8: fix(privacy-center): resolve mobile/org_user_id as contact for mobile-only logins
-
-### Patch Changes
-
-- 8145b3d: Privacy Center: when `ledgerBaseUrl` is not provided, consent reads/writes (user-consents, group purposes, manage-consent, receipts list, receipt PDF) fall back to the legacy Python `/dsar/privacy-center` endpoints and payloads instead of 404ing against `${baseUrl}/public/...`, and the DSAR form's ledger picker overlay is skipped. Fixes the Privacy Center showing "No Data" for integrations without a deployed Go ledger.
-
-## 10.0.0-beta.0
-
-### Major Changes
-
-- route consent writes & Privacy Center reads through the Go ledger (ledgerBaseUrl)
-
-## 9.4.0
-
-### Minor Changes
-
-- 9f7f7d5: feat(consent-sdk-react): add RedactoNoticeAssisted (agent-assisted OTP consent) + starter loan demo
-- add notice assisted and fix ui/ux
-
-## 9.4.0-beta.0
-
-### Minor Changes
-
-- feat(consent-sdk-react): add RedactoNoticeAssisted (agent-assisted OTP consent) + starter loan demo
-
-## 9.3.0
-
-### Minor Changes
-
-- 0642145: show empty blank screen when no data visible
-
-### Patch Changes
-
-- bd3c598: fix(consent-sdk-react): restore erasure consent-revoke confirmation modal
-- fix(consent-sdk-react): restore erasure consent-revoke confirmation modal
-
-## 9.3.0-beta.1
-
-### Patch Changes
-
-- fix(consent-sdk-react): restore erasure consent-revoke confirmation modal
-
-## 9.3.0-beta.0
-
-### Minor Changes
-
-- show empty blank screen when no data visible
-
-## 9.2.0
-
-### Minor Changes
-
-- 06a735c: keep revoked-consent purposes raisable in privacy-center DSAR forms
-- Refactor Privacy Center UX: remove "active" qualifier from product chip purpose counts, implement single-select product chips with an inline purpose panel, redesign the grouped DSAR product picker experience, and add a fully internationalized "My Receipts" tab for consent receipt management.
-- 45b7b2b: download receipt and product level grievance form
-
-### Patch Changes
-
-- b132a29: fix(consent-sdk-react): drop "active" qualifier from product chip purpose count
-
-## 9.2.0-beta.3
-
-### Minor Changes
-
-- Refactor Privacy Center UX: remove "active" qualifier from product chip purpose counts, implement single-select product chips with an inline purpose panel, redesign the grouped DSAR product picker experience, and add a fully internationalized "My Receipts" tab for consent receipt management.
-
-## 9.2.0-beta.2
-
-### Patch Changes
-
-- fix(consent-sdk-react): drop "active" qualifier from product chip purpose count
-
-## 9.2.0-beta.1
-
-### Minor Changes
-
-- download receipt and product level grievance form
-
-## 9.2.0-beta.0
-
-### Minor Changes
-
-- keep revoked-consent purposes raisable in privacy-center DSAR forms
-
-## 9.1.0
-
-### Minor Changes
-
-- remove hard coded 30 days values
-
-## 9.0.0
-
-### Major Changes
-
-- bugs fix
-
-## 8.0.0
-
-### Major Changes
-
-- enhance ui/ux
-
-## 7.3.0
-
-### Minor Changes
-
-- change branding path
-
-## 7.2.0
-
-### Minor Changes
-
-- bugs fix
-
-### Patch Changes
-
-- 7df3e20: Thread the clicked card's `product_uuid` through the privacy center's revoke/regrant/renew flow so purposes shared across multiple product cards mutate the correct card instead of falling back to action-implied scoping (which is ambiguous when two cards share the same state). Adds an optional `productUuid` parameter to the public `manageConsent` API; existing callers that omit it keep the prior server-side fallback behaviour.
-
-## 7.1.0
-
-### Minor Changes
-
-- update responsivenss
-
-## 7.0.0
-
-### Major Changes
-
-- configurable privacy center SDK
-- 331cbad: Apply org-level branding in `RedactoPrivacyCenter`. The privacy center now fetches `/user/api/0/public/org-branding/by-slug/{slug}` on mount and uses the response to:
-  - Swap the sidebar header avatar for the org's `icon_url` (collapsed) or wide `logo_url` (expanded).
-  - Show `brand_name` as the sidebar title.
-  - Hide the "Powered by Redacto" footer when `hide_platform_branding` is `true`.
-  - Apply the org's `theme` colors at runtime as `--pc-*` CSS custom-property overrides on `document.documentElement`. Primary/secondary hover and active variants are auto-derived. Cleared on unmount so the host page reverts to defaults.
-
-  **Breaking changes:**
-  - Removed dark mode from the privacy center. `ThemeProvider`, `useTheme`, `ThemeToggle`, and `ThemeTransitionOverlay` are deleted, the `[data-theme="dark"]` CSS block is gone, and the moon/sun toggle no longer appears in the navbar.
-  - Removed the `theme` prop from `RedactoPrivacyCenter`. The privacy center is now light-only; org-branding theme colors are applied on top.
-
-  Falls back to the previous initials avatar, slug-derived name, and SDK default colors when the branding response is unavailable.
-
-## 6.0.0
-
-### Major Changes
-
-- update Manage Consent
-
-## 5.3.0
-
-### Minor Changes
-
-- notification hub
-
-## 5.2.0
-
-### Minor Changes
-
-- docs update
-
-## 5.1.0
-
-### Minor Changes
-
-- update docs
-
-## 5.0.0
-
-### Major Changes
-
-- add privacy center sdk
-
-## 4.0.0
-
-### Major Changes
-
-- add privacy center sdk to react native and react
-
-## 3.6.0
-
-### Minor Changes
-
-- refactor payload to add language
-
-## 3.5.0
-
-### Minor Changes
-
-- add legacy api
-
-## 3.4.0
-
-### Minor Changes
-
-- feat: added notce 2.0
-
-## 3.3.0
-
-### Minor Changes
-
-- update support for submit API
-
-## 3.2.0
-
-### Minor Changes
-
-- enhance PurposeItem component to track initial data elements
-
-## 3.1.0
-
-### Minor Changes
-
-- purpose expiry for null validity
-
-## 3.0.0
-
-### Major Changes
-
-- downgrade react version in sdk
-
-## 2.1.0
-
-### Minor Changes
-
-- accessibility voice over cahnges
-
-## 2.0.0
-
-### Major Changes
-
-- added accessibility
-
-## 1.4.0
-
-### Minor Changes
-
-- fix language scroll issue
-
-## 1.3.0
-
-### Minor Changes
-
-- fix language scroll issue
-
-## 1.2.0
-
-### Minor Changes
-
-- chore: updated API routes
-
-## 1.1.0
-
-### Minor Changes
-
-- feat: add accessibility and fixes transalations
-
-## 1.0.0
-
-### Major Changes
-
-- Inline consent sdk added
-
-### Patch Changes
-
-- 0eac64c: Added base url as prop