Skip to content

ErrorBoundary silently discards caught errors with no logging or reporting #11

Description

@abayomicornelius

src/components/common/ErrorBoundary.tsx implements getDerivedStateFromError to show a fallback UI but has no componentDidCatch(error, info) to log the error to the console or forward it to an error-tracking service. In production this means React render crashes are completely invisible to the team — users just see "Something went wrong" with no trace left anywhere.

Add componentDidCatch logging (and ideally a hook point for Sentry/similar) before this ships to production users.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingenhancementNew feature or request

    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