Skip to content

Get rid of the ctry! & cexpect! macros #860

Closed
@jyn514

Description

@jyn514

Pretty sure we can literally just replace ctry! with ? now given that errors without an explicit status code are treated as 500s (or if we can't, could try and make it so that we can). That would allow changing cexpect! usage into .ok_or_else(|| err_msg(...))?.

Originally posted by @Kixiron and @Nemo157 in #858 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-frontendArea: Web frontendC-technical-debtCategory: This makes the code harder to read and modify, but has no impact on end usersP-lowLow priority issuesS-blockedStatus: marked as blocked ❌ on something else such as an RFC or other implementation work.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions