docs: module call response, error codes, remove scenarios
CI / check (push) Successful in 16s
CI / publish (push) Has been skipped

This commit is contained in:
edmand46
2026-09-17 12:27:52 +03:00
parent 6f37b00fb4
commit 4ab406c5cd
3 changed files with 27 additions and 3 deletions
+12
View File
@@ -2,6 +2,18 @@
## Unreleased
- `client.modules.call` resolves to `CallModuleFunctionClientResponse`, which
carries only `result`. Console output, the kernel call log and `error` are
no longer part of the player response; they stay on the platform dry run.
- Module business errors reject with `RudderHttpError` (`status` 422, body
`{ error, code, requestId }`). `code` is defined by the module and is an
open string.
- `RudderErrorCodes` and the `RudderErrorCode` type are no longer exported
from the package. The generated platform codes are now only `forbidden` and
`row_referenced`; the scenario and quest codes (`early_completion`,
`level_not_reached`, `node_not_active`, `objectives_incomplete`,
`run_expired`, `run_not_active`, `scenario_not_active`, `unknown_run`) are
removed with those domains. Compare `error.code` with string literals.
- Login and token refresh send `platform: 'web'` and, when the new optional
`appVersion` client option is set, `appVersion`. The backend stores them on
the player for segment rules (`player.platform`, `player.appVersion`).