@redacto.io/consent-sdk-react 9.2.0-beta.2 → 9.3.0-beta.0

package/.turbo/turbo-build.log

@@ -1,26 +1,25 @@
-
-
-> @redacto.io/consent-sdk-react@9.1.0 build /Users/sadanmianredacto/Developer/redacto/consent-sdk/packages/consent-sdk-react
-> 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          237.00 KB
-CJS dist/privacy-center.js 2.02 MB
-CJS ⚡️ Build success in 125ms
-ESM dist/index.mjs          226.91 KB
-ESM dist/chunk-6A665OPR.mjs 841.00 B
-ESM dist/privacy-center.mjs 1.99 MB
-ESM ⚡️ Build success in 131ms
-DTS Build start
-DTS ⚡️ Build success in 5254ms
-DTS dist/index.d.mts          6.12 KB
-DTS dist/privacy-center.d.mts 28.52 KB
-DTS dist/index.d.ts           6.12 KB
-DTS dist/privacy-center.d.ts  28.52 KB
+
+> @redacto.io/consent-sdk-react@9.2.0 build /Users/sadanmianredacto/Developer/redacto/consent-sdk/packages/consent-sdk-react
+> 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          237.00 KB
+CJS dist/privacy-center.js 2.16 MB
+CJS ⚡️ Build success in 59ms
+ESM dist/chunk-6A665OPR.mjs 841.00 B
+ESM dist/index.mjs          226.91 KB
+ESM dist/privacy-center.mjs 2.12 MB
+ESM ⚡️ Build success in 65ms
+DTS Build start
+DTS ⚡️ Build success in 2407ms
+DTS dist/index.d.mts          6.12 KB
+DTS dist/privacy-center.d.mts 30.45 KB
+DTS dist/index.d.ts           6.12 KB
+DTS dist/privacy-center.d.ts  30.45 KB

package/.turbo/turbo-test.log

@@ -0,0 +1,203 @@
+
+> @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

@@ -0,0 +1,6 @@
+
+> @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,5 +1,29 @@
 # @redacto.io/consent-sdk-react
 
+## 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