@eturnity/eturnity_reusable_components 9.37.2 → 9.37.3

package/README.md

@@ -10,7 +10,8 @@ npm install @eturnity/eturnity_reusable_components
 
 ### Setting up the theme
 
-The library now includes its own theme. You need to wrap your application with the `ThemeProvider` component from this library.
+The library now includes its own theme. You need to wrap your application with
+the `ThemeProvider` component from this library.
 
 **Recommended approach - Using the exported theme:**
 
@@ -66,7 +67,8 @@ import InputText from '@eturnity/eturnity_reusable_components/src/components/inp
 
 ### Overriding the theme (optional)
 
-If you need to customize or override the theme, you can pass your own theme when installing the plugin:
+If you need to customize or override the theme, you can pass your own theme when
+installing the plugin:
 
 ```javascript
 import EturnityComponentsPlugin, {
@@ -124,22 +126,32 @@ Customers load provided files from jsDelivr using stable tag-based URLs:
 <script src="https://cdn.jsdelivr.net/npm/@eturnity/eturnity_reusable_components@latest-consent-bridge/dist/eturnity-consent-bridge.min.js"></script>
 ```
 
-Consent bridge integration documentation is maintained in `docs/eturnity-consent-bridge.md` and published to:
+Consent bridge integration documentation is maintained in
+`docs/eturnity-consent-bridge.md` and published to:
 
 ```text
 https://cdn.jsdelivr.net/npm/@eturnity/eturnity_reusable_components@latest-consent-bridge/dist/eturnity-consent-bridge.md
 ```
 
-Provided files and docs are configured in `provided-assets.config.js`. Script and doc entries can both define their own `versionTag` (for example `latest-consent-bridge`). Because customers keep these URLs unchanged, we update what they receive by moving those npm dist-tags to a published package version.
+Provided files and docs are configured in `provided-assets.config.js`. Script
+and doc entries can both define their own `versionTag` (for example
+`latest-consent-bridge`). Because customers keep these URLs unchanged, we update
+what they receive by moving those npm dist-tags to a published package version.
 
 ### Build and publish behavior
 
-- `npm run build` runs `vite build` (library), `npm run build:provided-files` (JS CDN bundles), and `npm run copy:provided-docs` (published docs).
-- `npm run build:provided-files` builds files listed in `provided-assets.config.js` into `dist/*.min.js`.
-- `npm run copy:provided-docs` copies docs listed in `provided-assets.config.js` into `dist/*.md`.
-- `npm run verify:provided-files` checks expected provided files exist in `dist/` and are non-empty.
-- `npm run verify:provided-docs` checks expected provided docs exist in `dist/` and are non-empty.
-- `prepack` and `prepublishOnly` run both verification steps to reduce broken publish risk.
+- `npm run build` runs `vite build` (library), `npm run build:provided-files`
+  (JS CDN bundles), and `npm run copy:provided-docs` (published docs).
+- `npm run build:provided-files` builds files listed in
+  `provided-assets.config.js` into `dist/*.min.js`.
+- `npm run copy:provided-docs` copies docs listed in `provided-assets.config.js`
+  into `dist/*.md`.
+- `npm run verify:provided-files` checks expected provided files exist in
+  `dist/` and are non-empty.
+- `npm run verify:provided-docs` checks expected provided docs exist in `dist/`
+  and are non-empty.
+- `prepack` and `prepublishOnly` run both verification steps to reduce broken
+  publish risk.
 
 ### Standard release steps
 
@@ -149,9 +161,11 @@ Provided files and docs are configured in `provided-assets.config.js`. Script an
 npm publish
 ```
 
-2. Optional: promote provided-asset tag(s) so customer script/doc URLs point to that version.
+2. Optional: promote provided-asset tag(s) so customer script/doc URLs point to
+   that version.
 
-Use this only if you want to update what customers receive from stable CDN tag URLs:
+Use this only if you want to update what customers receive from stable CDN tag
+URLs:
 
 Script options (`--dry-run`, `--version=…`, `--name=…`, and combinations)
 
@@ -196,7 +210,8 @@ Optional tuning via environment variables:
 
 ### Optional rollback (re-point customer URL to older stable package)
 
-If a promoted version is broken, you can optionally promote a previously published version:
+If a promoted version is broken, you can optionally promote a previously
+published version:
 
 ```bash
 npm run promote:provided-files-tag -- --version=<older-published-version>
@@ -217,11 +232,19 @@ npm run promote:provided-files-tag -- --version=9.15.2
 
 Unit tests are Jest + `@vue/test-utils`, co-located with each component as
 `componentName.spec.js`. Run a single spec with `pnpm test <path>` or the full
-suite with `pnpm test`. See [`docs/component-testing.md`](docs/component-testing.md)
-for how we write tests (conventions, the TDD workflow, and using Claude Code).
+suite with `pnpm test`. See
+[`docs/component-testing.md`](docs/component-testing.md) for how we write tests
+(conventions, the TDD workflow, and using Claude Code).
 
 ## CI and pull requests
 
-Opening or updating a pull request runs **Bitbucket Pipelines** ([`bitbucket-pipelines.yml`](bitbucket-pipelines.yml)): install with pnpm, **`pnpm test`**, then **`pnpm run build`**. PRs are expected to pass this pipeline.
+Opening or updating a pull request runs **Bitbucket Pipelines**
+([`bitbucket-pipelines.yml`](bitbucket-pipelines.yml)): install with pnpm,
+**`pnpm test`**, then **`pnpm run build`**. PRs are expected to pass this
+pipeline.
 
-**Blocking merges on failure** is configured in **Bitbucket repository settings** (not in this repo): enable merge checks that require a successful pull-request build—for example a minimum number of successful builds for the PR, or “require passing pipelines” if your plan supports it. Until that is enabled, a red pipeline is visible but may not stop merges automatically.
+**Blocking merges on failure** is configured in **Bitbucket repository
+settings** (not in this repo): enable merge checks that require a successful
+pull-request build—for example a minimum number of successful builds for the PR,
+or “require passing pipelines” if your plan supports it. Until that is enabled,
+a red pipeline is visible but may not stop merges automatically.

package/dist/eturnity-consent-bridge.md

@@ -1,20 +1,24 @@
 # eturnityConsentBridge
 
-Lightweight browser bridge for synchronizing consent-related cookie payloads between a host page and an embedded Eturnity iframe via `postMessage`.
+Lightweight browser bridge for synchronizing consent-related cookie payloads
+between a host page and an embedded Eturnity iframe via `postMessage`.
 
 ## Overview
 
-`eturnityConsentBridge` is a public browser/CDN script that exposes a global function:
+`eturnityConsentBridge` is a public browser/CDN script that exposes a global
+function:
 
 - `window.eturnityConsentBridge(...)`
 - `eturnityConsentBridge(...)`
 
-It is designed for third-party embedding on customer websites and supports multiple bridge instances (multiple iframes) on the same page.
+It is designed for third-party embedding on customer websites and supports
+multiple bridge instances (multiple iframes) on the same page.
 
 ## Features
 
 - Global API for plain HTML and JavaScript-based script injection flows
-- Safe message routing per iframe instance using `event.source` and origin checks
+- Safe message routing per iframe instance using `event.source` and origin
+  checks
 - Idempotent initialization for repeated calls with the same iframe ID
 - Non-throwing input validation (returns `null` on invalid init input)
 - Cookie fallback persistence and replay on iframe sync-ready handshake
@@ -57,7 +61,8 @@ Initialization returns:
 - instance object on success
 - `null` when validation fails
 
-The iframe can be missing at init time; the bridge will keep trying to resolve it during message handling.
+The iframe can be missing at init time; the bridge will keep trying to resolve
+it during message handling.
 
 ## Message Contract
 
@@ -88,9 +93,12 @@ Stored cookie replay can be triggered in two safe ways:
 - **on init**: right after bridge initialization (`eturnityConsentBridge(...)`)
 - **on handshake**: when iframe sends `eturnity_<type>_cookie_sync_ready`
 
-The init replay exists to avoid reload race conditions where the iframe handshake might be sent before the host bridge is fully attached.
+The init replay exists to avoid reload race conditions where the iframe
+handshake might be sent before the host bridge is fully attached.
 
-Delete events are also synchronized: when iframe sends `eturnity_<type>_cookie_delete`, host removes that entry from its cache and then emits `eturnity_<type>_cookie_sync` with `{ cookieName, isDeleted: true }`.
+Delete events are also synchronized: when iframe sends
+`eturnity_<type>_cookie_delete`, host removes that entry from its cache and then
+emits `eturnity_<type>_cookie_sync` with `{ cookieName, isDeleted: true }`.
 
 ## API
 
@@ -116,7 +124,8 @@ Destroys one bridge instance.
 
 ### `eturnityConsentBridge.destroyAll()`
 
-Destroys all bridge instances and removes the shared `message` listener when no instances remain.
+Destroys all bridge instances and removes the shared `message` listener when no
+instances remain.
 
 ### `BridgeInstance.destroy()`
 
@@ -132,7 +141,8 @@ type BridgeOptions = {
 ```
 
 - **`type`** (required): selects internal message/cookie namespace
-- **`logs`** (optional, default `false`): enables verbose console logging for this instance
+- **`logs`** (optional, default `false`): enables verbose console logging for
+  this instance
 
 Unknown option keys are ignored.
 
@@ -185,7 +195,8 @@ eturnityConsentBridge.destroyAll()
 ### `Iframe ... was not found during initialization`
 
 - Verify iframe ID matches exactly.
-- If iframe is rendered later, you can initialize early; bridge resolves context again during runtime.
+- If iframe is rendered later, you can initialize early; bridge resolves context
+  again during runtime.
 
 ### `Could not resolve iframe origin`
 
@@ -193,15 +204,22 @@ eturnityConsentBridge.destroyAll()
 
 ### `Ignoring ... due to origin mismatch`
 
-- Host and iframe messaging origins must match the iframe `src` origin resolved by the bridge.
+- Host and iframe messaging origins must match the iframe `src` origin resolved
+  by the bridge.
 
 ### Why replay may happen before `cookie_sync_ready`
 
-- This is expected behavior: replay on init is intentional and does not depend on handshake timing.
-- In some page-load orders, the iframe can emit `cookie_sync_ready` before the host bridge listener is attached; in that case you may not see a handshake log.
-- This does not break integration: the iframe consumes `eturnity_<type>_cookie_sync` messages directly, and `cookie_sync_ready` is only a replay signal from iframe to host.
+- This is expected behavior: replay on init is intentional and does not depend
+  on handshake timing.
+- In some page-load orders, the iframe can emit `cookie_sync_ready` before the
+  host bridge listener is attached; in that case you may not see a handshake
+  log.
+- This does not break integration: the iframe consumes
+  `eturnity_<type>_cookie_sync` messages directly, and `cookie_sync_ready` is
+  only a replay signal from iframe to host.
 
 ### Cookie warning on non-HTTPS host
 
-- The bridge writes cookies with `Secure`; on non-HTTPS pages browsers may reject persistence.
+- The bridge writes cookies with `Secure`; on non-HTTPS pages browsers may
+  reject persistence.
 - Use HTTPS in production embedding environments.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eturnity/eturnity_reusable_components",
-  "version": "9.37.2",
+  "version": "9.37.3",
   "files": [
     "dist",
     "src"

package/src/assets/svgIcons/_readme.md

@@ -2,6 +2,7 @@
 
 colors in icons will be replaced in paths only.
 
-if an svg contain a rect or polygon or circle you want color to be applied on, convert them into path using:
+if an svg contain a rect or polygon or circle you want color to be applied on,
+convert them into path using:
 
 https://thednp.github.io/svg-path-commander/convert.html

package/src/components/filter/parentDropdown.vue

@@ -65,6 +65,7 @@
     display: flex;
     align-items: center;
     gap: 8px;
+    white-space: nowrap;
   `
 
   const Counter = styled.div`

package/src/assets/svgIcons/meter.svg

@@ -1,3 +0,0 @@
-<svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg">
-<path d="M7.99988 2C9.38419 2 10.7375 2.41068 11.8885 3.17969C13.0397 3.94883 13.9369 5.04227 14.4667 6.32129C14.9964 7.60027 15.1351 9.00747 14.8651 10.3652C14.6292 11.551 14.0911 12.6534 13.3065 13.5654L13.2294 13.6367C13.0359 13.7809 12.7574 13.7575 12.578 13.5781C12.3736 13.3731 12.3756 13.0424 12.5614 12.8203C13.1208 12.1523 13.5272 11.3687 13.7509 10.5254L13.8358 10.1611C14.0654 9.00695 13.9473 7.80988 13.4969 6.72266C13.0747 5.70353 12.3778 4.82341 11.4862 4.17871L11.3055 4.05273C10.3271 3.399 9.17662 3.0498 7.99988 3.0498C6.82316 3.04985 5.67263 3.39898 4.69421 4.05273C3.71591 4.70646 2.95314 5.63563 2.50281 6.72266L2.42273 6.92773C2.03943 7.95934 1.94869 9.07895 2.16394 10.1611C2.3593 11.143 2.79919 12.0571 3.43835 12.8203C3.62426 13.0425 3.62633 13.3731 3.42175 13.5781L3.33875 13.6455C3.16397 13.7608 2.93614 13.7604 2.77039 13.6367L2.69324 13.5654C2.00668 12.7673 1.50892 11.8234 1.23718 10.8057L1.13464 10.3652C0.881519 9.09233 0.987587 7.77593 1.43835 6.5625L1.53308 6.32129C2.02976 5.12224 2.84939 4.08667 3.89832 3.32812L4.11121 3.17969C5.26224 2.41066 6.61558 2.00004 7.99988 2ZM10.1093 5.1875C10.2817 4.97192 10.5968 4.93699 10.8124 5.10938C11.028 5.28188 11.063 5.59687 10.8905 5.8125L9.12781 8.01465C9.35847 8.27842 9.49988 8.62208 9.49988 9C9.49988 9.82843 8.82831 10.5 7.99988 10.5C7.17154 10.4999 6.49988 9.82836 6.49988 9C6.49988 8.17164 7.17154 7.50011 7.99988 7.5C8.08232 7.5 8.16324 7.50771 8.24207 7.52051L10.1093 5.1875ZM7.99988 8.5C7.72383 8.50011 7.49988 8.72392 7.49988 9C7.49988 9.27608 7.72383 9.49989 7.99988 9.5C8.27602 9.5 8.49988 9.27614 8.49988 9C8.49988 8.72386 8.27602 8.5 7.99988 8.5Z" fill="#263238"/>
-</svg>