Redis vector store: unEscapeSpecialChars only reverses -, causing JSON.parse failure on metadata read

[mshahrouri]

Describe the bug

When retrieving documents from a Redis vector store via Retrieval Playground, similarity search fails with: Expected property name or '}' in JSON at position 1
This happens on any document whose metadata contains RediSearch special characters other than -
after modifying unEscapeSpecialChars in usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/vectorstores/Redis/utils.js to become:
const unEscapeSpecialChars = (str) => { return str.replace(/\\([,.<>{}[\]"':;!@#$%^&*()\-+=~])/g, '$1'); };
Playground works as expected

To Reproduce

1- Setup a Redis vector store node
2- upsert a document whose metadata contains colon or double quote
3- in Retrival Playground run similarity search
4- JSON error appears

Expected behavior

Retrieval should succeed regardless of which RediSearch-reserved characters appear in the document metadata.

Screenshots

No response

Flow

No response

Use Method

Docker

Flowise Version

3.1.2

Operating System

Linux

Browser

None

Additional context

No response

[Abhiiishek44]

Hi, I’d like to work on this issue if it’s available.

From the bug details, it looks like Redis vector store metadata is escaped before storage/search, but unEscapeSpecialChars does not fully reverse all RediSearch-reserved characters during retrieval. Because of that, metadata containing characters like : or " can remain escaped and cause JSON.parse() to fail in Retrieval Playground.

I’ll check the source TypeScript implementation for the Redis vector store, update the unescape logic to match the escaped special characters, and add/verify a case for metadata containing reserved characters such as colon and double quotes.

Please let me know if this approach sounds good.