Skip to content

The errors generated by RESPTokenDecodable.init(fromRESP) need improved #225

@adam-fowler

Description

@adam-fowler

Currently most of the RESPTokenDecodable.init(fromRESP) implementations throw a RESPParsingError as there is no alternative. In the context of decoding a RESPToken this error is pretty useless. We need a decoding error type which provides more information, but without additional cost to the decoding process.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions