0.5.1: custom quest metrics no-op, doc fix
This commit is contained in:
@@ -1,5 +1,12 @@
|
||||
# Changelog
|
||||
|
||||
## 0.5.1
|
||||
|
||||
- `QuestMetrics` / `reportProgress`: custom free-text metrics no longer
|
||||
progress quests. Report a released catalog counter slug instead.
|
||||
`purchaseOffer` / `purchaseItem` helpers are unchanged (server-side shop
|
||||
fan-out).
|
||||
|
||||
## 0.5.0
|
||||
|
||||
- `client.auth.loginWithCustom({ customData, region?, language?, nickname? })`
|
||||
|
||||
+1
-1
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "@rudder/js-sdk",
|
||||
"version": "0.5.0",
|
||||
"version": "0.5.1",
|
||||
"publishConfig": {
|
||||
"registry": "https://hub.rudder.build/api/packages/rudder/npm/"
|
||||
},
|
||||
|
||||
@@ -3,8 +3,9 @@
|
||||
*
|
||||
* Purchase metrics are reported automatically server-side by the shop
|
||||
* purchase fan-out, so these helpers exist mainly to name the format
|
||||
* instead of hardcoding it. Any other metric is a custom string reported via
|
||||
* {@link QuestsService.reportProgress}.
|
||||
* instead of hardcoding it. Catalog counter slugs are reported via
|
||||
* {@link QuestsService.reportProgress}. Custom free-text metrics no longer
|
||||
* progress quests — they no-op at runtime.
|
||||
*/
|
||||
|
||||
/** Metric for purchasing a store offer; auto-reported on purchase. */
|
||||
|
||||
Reference in New Issue
Block a user