Skip to content

chore: double check public/private visibility for our errors #3359

Open
@ramfox

Description

@ramfox

We have some cases where a publicly available error wraps a private error. This is unintentional, and those private errors should likely be made public, or at least double-checked.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions