Switched to RESP3; XRANGE transforms object entries as map but XREAD does not

[vvashisht]

Description

If I switch back to RESP2, both XRANGE and XREAD transform object entries to maps.

Is this intentional? Or perhaps a regression bug?

Node.js Version

22.16.0

Redis Server Version

8.0.1

Node Redis Version

5.1.1

Platform

Ubuntu 24 on WSL2

Logs

[nkaradzhov]

Hi @vvashisht,

As per the docs, this is the expected behavior for XREAD in Resp3.

In principal, it is a good idea to provide the same interface for XREAD regardless of protocol, so we will consider making this change. @elena-kolevska, @bobymicroby should that be considered a breaking change?

Btw, while investigating this, i found that, as per the docs, XREAD should throw an error if used with Resp3 and without the unstableResp3 flag. So that will be addressed in the next patch release