@xenia-martech/sdk-js 1.0.0-dev.29 → 1.0.0-dev.33

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -10,16 +10,14 @@ The official Xenia Marketer SDK for **web (pull) channels**. Drop in one wrapper
10
10
 
11
11
  One client, four jobs. Everything below rides on the same identity/attribution state, so you never wire these together by hand:
12
12
 
13
- ```mermaid
14
- flowchart LR
15
- App["Your app<br/>(browser or server)"] -->|"1 · track()"| EV["POST /api/events/v1<br/>analytics + journey triggers"]
16
- App -->|"2 · request() / webhook()"| WH["Journey webhook endpoint"]
17
- WH -->|"xeniaActions in the reply"| App
18
- App -->|"3 · resolve()"| RS["POST /api/personalization/resolve<br/>REST, production path"]
19
- RS -->|"personalized content"| App
20
- EV --> J["Journey Orchestrator"]
21
- WH --> J
22
- ```
13
+ <!--
14
+ Rendered image, not Mermaid — npmjs.com does not render Mermaid diagrams.
15
+ The PNG lives in assets/ and ships in the package (see package.json "files").
16
+ Served from the npm tarball via jsdelivr, pinned to the `dev` dist-tag because
17
+ the package is currently prerelease-only (latest is a 1.0.0-dev.* build). Once
18
+ a stable release exists, drop `@dev` so it tracks `latest`.
19
+ -->
20
+ ![Your app calls track() → POST /api/events/v1, request()/webhook() → the journey webhook endpoint (whose reply carries xeniaActions), and resolve() → POST /api/personalization/resolve; events and webhooks feed the Journey Orchestrator.](https://cdn.jsdelivr.net/npm/@xenia-martech/sdk-js@dev/assets/sdk-request-flow.png)
23
21
 
24
22
  | Feature | What it does | Call it with |
25
23
  |---|---|---|
Binary file
@@ -1817,6 +1817,17 @@ var STYLES = `
1817
1817
  border: 0; border-radius: var(--xenia-cta-radius, 8px); padding: var(--xenia-cta-padding, 8px 14px);
1818
1818
  font-size: var(--xenia-cta-size, 14px); font-family: inherit; cursor: pointer; }
1819
1819
  .xenia-wheel-spin:disabled { opacity: 0.6; cursor: default; }
1820
+ /* The spinner face and the win/loss screens are siblings toggled via the 'hidden' attribute \u2014
1821
+ during crossFadeReveal's ~320ms crossfade, BOTH the outgoing and incoming screen are visible
1822
+ (not hidden) at once, so without this they'd stack in normal block flow and roughly double
1823
+ this box's height for that window. Since .xenia-modal's flexbox re-centers on every height
1824
+ change, that briefly-doubled height yanks the whole card to a new position with ZERO
1825
+ animation \u2014 right before the scale-down transition starts animating smoothly from that
1826
+ already-jumped spot, reading as "not scaling from center". Grid-stacking every child into the
1827
+ same cell (sized to the tallest non-hidden one) makes the outgoing/incoming screens overlay in
1828
+ place instead of stacking, so there is no discrete height jump to correct for. */
1829
+ .xenia-spin-wheel { display: grid; }
1830
+ .xenia-spin-wheel > * { grid-area: 1 / 1; }
1820
1831
  /* No animation/transform here \u2014 spin-wheel's win/loss screens are ALWAYS full
1821
1832
  custom HTML now (winHtml/lossHtml), never this class's own generated icon/title/prize/cta
1822
1833
  content (those sub-classes below are unreachable dead CSS, kept only for backwards-compat with