Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Align return type of captureMessage to captureThrowable #39

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from
Draft

Align return type of captureMessage to captureThrowable #39

wants to merge 6 commits into from

Commits on Nov 18, 2024

  1. Improve sentry:test command 

    This now has three different modes:

- for testing message capturing
- for testing exception handling
- for testing error handling
    @kdambekalns
    kdambekalns committed Nov 18, 2024
    Configuration menu
    Copy the full SHA
    67042e4 View commit details
    Browse the repository at this point in the history

  2. Register Sentry early in the bootstrap 

    Instead of setting up the Sentry client when something needs to be
sent to Sentry in the `SentryStorage` this initializes the Sentry
client as soon as Flow's object management is usable.

This allows to use Sentry to capture exceptions and errors as early
as possible.
    @kdambekalns
    kdambekalns committed Nov 18, 2024
    Configuration menu
    Copy the full SHA
    5cd55ba View commit details
    Browse the repository at this point in the history

  3. Use Sentry default integrations 

    This activates the default integrations shipped with Sentry again.

This adds information about installed Composer packages, the request,
frame context and environment.

Through this, some "custom" tags can be dropped, as the information is
included by the default integrations.

Since Sentry registers an error handler, errors not handled by the
exception handler will also be recorded in Sentry.
    @kdambekalns
    kdambekalns committed Nov 18, 2024
    Configuration menu
    Copy the full SHA
    6e93aff View commit details
    Browse the repository at this point in the history

  4. "Re-tag" when capturing to Sentry 

    There may have been changes after Sentry was initialised first, so
re-run `setTags()` when sending events to Sentry.
    @kdambekalns
    kdambekalns committed Nov 18, 2024
    Configuration menu
    Copy the full SHA
    f07e071 View commit details
    Browse the repository at this point in the history

  5. Add log entries as breadcrumbs for Sentry events

    @kdambekalns
    kdambekalns committed Nov 18, 2024
    Configuration menu
    Copy the full SHA
    0fd62e3 View commit details
    Browse the repository at this point in the history

  6. Align return type of captureMessage to captureThrowable

    @kdambekalns
    kdambekalns committed Nov 18, 2024
    Configuration menu
    Copy the full SHA
    b9ae6f1 View commit details
    Browse the repository at this point in the history