widget-web-component 1.4.0 → 1.5.0-dev

package/README.md

@@ -128,3 +128,36 @@ Query string, hash and trailing slash are stripped from a valid URL.
 
 > ⚠️ Only the URL **format** is validated, not the destination. The widget will only
 > work if `apiUrl` points to a valid Belender environment.
+
+---
+
+## 🔧 Environment config (`WidgetConfig`)
+
+`runtimeEnv` and `notificationsUrl` are **environment configuration** — they describe
+*which* Belender backend the widget talks to. These values are passed at initialization
+time via `initBelenderComponent(config)`, not as HTML attributes.
+
+```js
+initBelenderComponent({
+  runtimeEnv: 'qa',
+  notificationsUrl: 'wss://ws.custom-funder.com',
+}).then((BelenderWebComponent) => {
+  customElements.define('belender-web-component', BelenderWebComponent);
+});
+```
+
+**When omitted**, each field falls back to automatic derivation from the hostname of
+`api-url` (e.g. `.qa.` → `qa`, `api.` prefix → notifications URL). This means you only
+need to pass config when `api-url` points to a **custom domain** outside Belender's
+naming conventions.
+
+**Fields are independent** — you can set any subset. Unset values still fall back to
+the automatic derivation.
+
+> ℹ️ `organization` and `scraperMock` are always derived automatically from `api-url`
+> and are not configurable by the host.
+
+| Field | Type | Valid values | Derived from `api-url` when omitted |
+|---|---|---|---|
+| `runtimeEnv` | string | `qa`, `dev`, `pro` | `.qa.` in hostname → `qa`, `.dev.` → `dev`, otherwise → `pro` |
+| `notificationsUrl` | string | Any `ws://` or `wss://` URL | `api.` prefix replaced with `notifications.` |