-
Notifications
You must be signed in to change notification settings - Fork 27
Integrate breadcrumbs #107
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
Conversation
Early review before doing docs and so on is appreciated @crbelaus can you take a look? 👀 |
I've pushed a small commit that adds a |
Ready to review again @crbelaus 🙌 |
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.
Ship it! 🚀
This change adds support for breadcrumbs as a first-class field on our occurrences.
Breadcrumbs are now a way to store a list of strings indicating in which order they were added, so they can be used to track which code was executed and on which order. They are managed per-process (which in Phoenix means per-request in general)
Ash
andSplode
was updated to match the new system