docs: module call response, error codes, remove scenarios
This commit is contained in:
@@ -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`).
|
||||
|
||||
Reference in New Issue
Block a user