-
Notifications
You must be signed in to change notification settings - Fork 110
Support any data to be passed by attach (replace attach_message)
#609
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
|
As discussed off-GitHub, we will combine |
Report::provide methodattach (replace attach_message)
# Conflicts: # packages/engine/bin/cli/src/main.rs # packages/engine/bin/hash_engine/src/main.rs # packages/engine/lib/error/src/lib.rs # packages/engine/lib/error/src/macros.rs
Alfred-Mountfield
left a comment
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.
I'm a big fan of how much this has simplified things.
Can you look through the comments for references to old things like "message", "provider" (in the wrong places), etc.
Co-authored-by: Alfred Mountfield <am@hash.ai>
Co-authored-by: Alfred Mountfield <am@hash.ai>
Co-authored-by: Alfred Mountfield <am@hash.ai>
Co-authored-by: Alfred Mountfield <am@hash.ai>
🌟 What is the purpose of this PR?
For convenience, we want to attach any data without implementing a trait.
🔗 Related links
🔍 What does this change?
attach_messagetoattachattach_messageErroris moved tocore, we need to work around that in the doc string📹 Demo