Skip to content

RESP3: Is the error prefix part of the spec or not? #24

@414owen

Description

@414owen

The redis website states:

Note that the error prefix is a convention used by Redis rather than part of the RESP error type.

But the RESP3 spec in this repo states:

The first word in the error is in upper case and describes the error code. The remaining string is the error message itself


These two statements seem to be in conflict.
I think that the RESP3 spec should specify whether the uppercase error code is mandatory, and hence whether clients can parse it as an error code, or have to include it as part of the error string.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions