Skip to content

Evaluate well-known errors for compatibility posture #4

@paddycarver

Description

@paddycarver

Our well-known errors, like ErrUnsupportedDataSource, are currently set as error values, not types. We may want to evaluate making them less well-known, or returning fmt.Errorf wrapped versions, to force people to use errors.As instead of doing equality comparisons. This would give us a more flexible posture for future changes than we currently have.

Metadata

Metadata

Assignees

No one assigned

    Labels

    breaking-changeThis will impact or improve our compatibility posture

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions