-
Consider this client scenario (even if not regular):
```
const ws = new WebSocket("...", { port: ... });
const kuzzle = new Kuzzle(ws, ...);
await kuzzle.connect();
await kuzzle.auth.login("local…
-
Is there any way to reverse-engineer the ID to get the filter back ?
I would like to use https://docs.kuzzle.io/core/2/api/controllers/realtime/list/ and be able to know which filter is what
-
## Current Behavior
Process using Kuzzle SDK is consuming every affected CPU
Thread dump of process have several hundreds of :
```
"Thread-555" #932 [977] daemon prio=5 os_prio=0 cpu=2405…
-
The plug-in seems to have been written for Kuzzle v1.x. It would be great to see an updated version that works for v2.
-
- http://kuzzle.io
- https://github.com/kuzzleio/kuzzle
-
Tried to use this in a production environment and after some debugging i found out that the code is outdated regarding how to use Kuzzle-SDK in vanilla js.
Here is the new code so you can update it…
-
Running `npm audit` reveals worrying high vulnerabilities.
## Expected Behavior
No vulnerability should be returned by `npm audit`
## Current Behavior
Below, a part of the logs I get when …
-
```
kuzzle.js:2 Uncaught TypeError: Cannot read property 'message' of undefined
at new i (kuzzle.js:2)
at WebSocket.client.onmessage (kuzzle.js:2)
```
-
## Expected Behavior
In a kuzzle without any users, AC should display the card `no user is defined`
## Current Behavior
First AC display that card, but click again on users and AC will show searc…
-
## For feature request
[The native promise after node v10 is fast enough](https://github.com/petkaantonov/bluebird#note
).
Since `async` / `await` is supported in node v7 or later, it can be …