-
# Description
Decoders are initialized at the root level of the plugin (inside the init fonction) it will be better to move all that logic of init at the place where it belong -> DecodersService
…
-
## Description
Also allows to not return a HTTP error code when payload is not valid
**Return a Partial error (~20x) when a payload was badly formatted or not successfully ingested.**
-
## Expected Behavior
Hook on "core:realtime:user:subscribe:after" should trigger the function.
## Current Behavior
Hook on "core:realtime:user:subscribe:after" does not trigger the function
##…
-
The `profile` object returned by some providers (e.g. GitHub's OAuth provider) may contain fields which have `null` values. Examples include GitHub's `company` field. When `lib/index.js` attempts to c…
-
The stack for errors is taken from kuzzle response, which is in most cases empty, and if not, most likely useless to developers.
A valid stack showing from where the sdk method was called would be …
-
## Description
The payloads collection contains raw payloads from the sensors for debugging and analyze purposes.
We should add API action to remove old payloads (e.g. every payloads older 2 wee…
-
We should notify users (in development) when they are using obsolete features.
Controllers should checks for deprecation (method, parameters, etc)
Each deprecation is then added to an array retu…
-
## Expected Behavior
`context.accessors.log.info` is working
## Current Behavior
`context.accessors.log.info` doesn't work after plugin start (e.g. in a controller action)
## Possible Solu…
-
## Expected Behavior
Creating and deleting a user in a loop should work fine.
## Current Behavior
At some point Kuzzle will throw an error when creating the same user saying it's credentials …
jenow updated
3 years ago
-
## Expected Behavior
Trying to load plugin rights with the `--securities` flag at startup fail with an error indicating that the controller/actions does not exists
## Current Behavior
Should …