Skip to content

avoid CatchableError as much as possible #18

Description

@Ivansete-status

This is motivated by this comment: #14 (comment)

We should avoid CatchableError as much as possible, use specific errors instead, and give more context to error messages

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions