@eventra_dev/eventra-cli 2.0.6 → 2.0.7
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 +4 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -131,6 +131,8 @@ trackFeature("purchase");
|
|
|
131
131
|
|
|
132
132
|
The second argument (`userId`, `properties`) is **not** used as the event name.
|
|
133
133
|
|
|
134
|
+
A literal name that violates either rule (too long, or a character outside the allowed set) is not truncated and not flagged as a dynamic occurrence - it's silently excluded from the scan result, with no warning and no diagnostic anywhere. It simply never appears in `eventra.json` after `sync`. If an event you expect to see is missing, check this before assuming a detection bug.
|
|
135
|
+
|
|
134
136
|
---
|
|
135
137
|
|
|
136
138
|
## What is ignored
|
|
@@ -188,6 +190,8 @@ eventra send --trust-endpoint
|
|
|
188
190
|
|
|
189
191
|
This records the endpoint in `eventra.local.json` (gitignored). If `eventra.json`'s `endpoint` later changes to a different value — e.g. a PR silently pointing it at another host — `send` blocks again until re-approved, so a committed config change alone can't redirect where your API key and events get sent.
|
|
190
192
|
|
|
193
|
+
Once `eventra.json` already commits an `endpoint`, that committed value is what events actually get sent to - `EVENTRA_ENDPOINT` only controls whether the approval prompt is skipped; its own value is not read or compared against anything in that case. `EVENTRA_ENDPOINT` becomes the real destination only when `eventra.json` has no `endpoint` set at all. In other words, setting the variable to point somewhere else does not redirect traffic away from an already-committed endpoint - it only means you won't be asked to approve it.
|
|
194
|
+
|
|
191
195
|
Network resilience:
|
|
192
196
|
|
|
193
197
|
- Up to 4 attempts with exponential backoff + jitter (capped at 8 s)
|