Explanation of issues when using GET and NX/XX/IFEQ together in SET command

[soloestoy]

No description provided.

[zuiderkwast]

Great. I have a very small suggestion.

[zuiderkwast]

I think it's a small disaster that the Reply section is missing on the website version of the docs.

The replies are documented in the files resp2_replies.json and resp3_replies.json. Assuming it will be included on the website some time in the future, we can consider improving this part too.

This is the man page version of the reply section:

REPLY
   RESP2
       Any of the following:

       • valkey-protocol(7) Nil reply: GET not given: Operation was aborted (conflict with one of the XX/NX options).

       • valkey-protocol(7) Simple string reply: OK.  GET not given: The key was set.

       • valkey-protocol(7) Nil reply: GET given: The key didn’t exist before the SET.

       • valkey-protocol(7) Bulk string reply: GET given: The previous value of the key.

   RESP3
       Any of the following:

       • valkey-protocol(7) Null reply: GET not given: Operation was aborted (conflict with one of the XX/NX options).

       • valkey-protocol(7) Simple string reply: OK.  GET not given: The key was set.

       • valkey-protocol(7) Null reply: GET given: The key didn’t exist before the SET.

       • valkey-protocol(7) Bulk string reply: GET given: The previous value of the key.