-
Notifications
You must be signed in to change notification settings - Fork 0
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
prepare for release #69
Conversation
This is broken because I don't know how to fix the move problem at the moment, there is a PR open that could address it but there's also probably a way to go around it which I can't come up with right now |
src/macros/event_with_options.rs
Outdated
/// Send a custom event as a title and a body | ||
/// NOTE: Try to minimise variation in tag values (avoid things like timestamps or ids). See note in lib docs! | ||
#[macro_export] | ||
macro_rules! event_with_options { |
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.
WDYT about extending the event! Instead of creating a new one? It could receive the EventOptions as an argument and pass it to $crate::Datadog::event_with_options
instead of $crate::Datadog::event
.
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 was debating the two options, I think it may make sense to expose just one macro
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.
Nice one 👍🏼
No description provided.