Skip to content

feat: implement typed errors on refactor branch. #1790

Description

@Hweinstock

Problem

We currently throw untyped errors in the refactor. This makes it difficult to classify errors for telemetry in the future, and also leads to brittle logic to determine the source of errors based on message.

Definition of Done

create an error classification system that makes it easy to:

  • determine the category of the error (ex. credentials expired, missing file, etc.).
  • determine the "source" of the error (is it the user, is it the CLI internally, is it a service endpoint?).
  • extend with new categories of errors.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions