Skip to content

Errors for invalid input are inconsistent #24

@rlinehan

Description

@rlinehan

On the SDK-side, we have some specific validations, such as for a cache_name that is None, that return InvalidInputError. However, our SDK-side validations always expect users to provide a correct type. When users don't, we end up sending a generic ClientSdkException - the generic exception for any error the SDK doesn't understand. This is inconsistent and may be confusing to users as to why sometimes they get one error and sometimes another.

From @gautamomento in #22 (review):

I see two ways to handle this:

1. Embed type-safety checks in our custom validations

2. When we wrap unknown exceptions - also send include the root exception

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions