Skip to content

use custom errors, no strings #161

@orangecms

Description

@orangecms

There are instances left where we currently return strings, i.e., Err<String>. That carries meaning at runtime, but not to for API use.
This can be done gradually and needs some thinking about naming.

Metadata

Metadata

Assignees

No one assigned

    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