Skip to content

Section for handling/reporting errors? #3

@thgaskell

Description

@thgaskell

Open for discussion. It would be good to have some general best practices set in place (even if implementation changes between projects). I think having good practices set in place early not only makes debugging easier, but also lets you develop quicker.

It sucks if errors are failing silently, or an error occurs and there's no proper handler set in place, causing the entire app to break. 💢

Some thoughts:

  • How should errors be reported at the application level?
  • Best practices for handling server errors on the client-side? (It can quickly turn into spaghetti code)
  • What should be reported to the client? What should be logged at the server level?

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