You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
const jsonString = await getAsync(key, `NOESCAPE ${path}`);
or
const jsonString = await getAsync(key, `NOESCAPE "${path}"`);
or
const jsonString = await getAsync(key, `NOESCAPE \"${path}\"`);
or
const jsonString = await getAsync(key, `\"NOESCAPE\" ${path}`);
or
const jsonString = await getAsync(`${key} NOESCAPE`, path);
How are these commands translated to redisClient?
I read the #9 , but the answer makes no sense to me. If all this module is doing is making RedisJson's commands work, there should be support for all its commands or some kind of list of limitations that this module can't do.
The RedisJson command: JSON.GET "key" NOESCAPE "somePath.someSubPath"
works flawlessly in the CLI.
This module is recommended by RedisJSON. But how the commands work are not clearly explained.
Thanks!
The text was updated successfully, but these errors were encountered:
I have tried so many ways to pass in the
NOESCAPE
otion to thejson_get
command. But it seems that is not supported.Then calling it like:
How are these commands translated to redisClient?
I read the #9 , but the answer makes no sense to me. If all this module is doing is making RedisJson's commands work, there should be support for all its commands or some kind of list of limitations that this module can't do.
The RedisJson command:
JSON.GET "key" NOESCAPE "somePath.someSubPath"
works flawlessly in the CLI.
This module is recommended by RedisJSON. But how the commands work are not clearly explained.
Thanks!
The text was updated successfully, but these errors were encountered: