Skip to content

Define/Refine error handling best practices and review/cleanup code #8773

@ColinKerr

Description

@ColinKerr

There are inconsistencies with how we handle errors in iTwin.js. The goal of this issue is to be a central point to agree upon best practices, document them and gather issues pointing to code that must be updated to be consistent with best practices.

I think a general rule of thumb to start with is:
We should not throw errors for normal behavior and we should not return status in exceptional cases.

Sub-issues

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