-
Notifications
You must be signed in to change notification settings - Fork 2
feat(breadcrumbs): add Breadcrumb and related enums to event type definitions #613
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.
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
base: master
Are you sure you want to change the base?
Conversation
Dobrunia
commented
Jan 15, 2026
- Introduced BreadcrumbLevel and BreadcrumbType enums for categorizing breadcrumbs.
- Added Breadcrumb type to represent events leading up to errors, including fields for timestamp, type, category, message, severity level, and associated data.
- Updated EventPayload to include a breadcrumbs field for tracking chronological events before an error.
…initions - Introduced BreadcrumbLevel and BreadcrumbType enums for categorizing breadcrumbs. - Added Breadcrumb type to represent events leading up to errors, including fields for timestamp, type, category, message, severity level, and associated data. - Updated EventPayload to include a breadcrumbs field for tracking chronological events before an error.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR adds breadcrumb tracking capabilities to the event system, enabling the capture of chronological events leading up to errors. The changes introduce two new enums for categorizing breadcrumbs, a Breadcrumb type definition, and integration into the existing EventPayload type.
Changes:
- Added BreadcrumbLevel enum with five severity levels (fatal, error, warning, info, debug)
- Added BreadcrumbType enum with six categorization types (default, request, ui, navigation, logic, error)
- Added Breadcrumb type with fields for timestamp, type, category, message, level, and arbitrary data
- Extended EventPayload with a breadcrumbs field to track chronological events before errors
- Bumped version from 1.3.1 to 1.3.2
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/typeDefs/event.ts | Added BreadcrumbLevel and BreadcrumbType enums, Breadcrumb type definition, and integrated breadcrumbs array into EventPayload; includes minor whitespace cleanup |
| package.json | Bumped version to 1.3.2 reflecting the new breadcrumb feature |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| """ | ||
| Breadcrumbs - chronological trail of events before the error | ||
| """ | ||
| breadcrumbs: [Breadcrumb!] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does it mean that breadcrumbs may be empty?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. Breadcrumbs may be empty if tracking is disabled via options, filtered out in beforeBreadcrumb, or if no events happened yet