Skip to content

Incorrect implementation of custom errors for some common error types #110

Description

@nikitawootten

Bug Report:

Some errors in errors.go are just instances of errors, and not custom types that implement the error interface.

Tests for errors such as ErrNotFound can not directly be done without searching for error content.

Expected Behavior

errors.As() allows you to test if a GoGM error is a specific type, such as a ErrNotFound, ErrConnection, etc..

Current Behavior

Many errors do not implement the error

Possible Solution

Correctly implement custom errors

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions