-
Notifications
You must be signed in to change notification settings - Fork 108
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
feat(gstd): stabilize program logs #4072
Conversation
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.
Similar approach is used in sails for a while.
I'm super against of macros here, so if you really want such functionality to be a part of gstd, I'd go with just gstd::msg::emit/emit_bytes(..) that recalls send with 0 value and 0 destination
@DennisInSky wdyt?
Also there's no actually need in testing this |
closing this since these kind of implementations could be added to sails dynamically |
Resolves # .
Different from
gstd::debug!
, developers may havelog
requirements while building programs in production, e.g. using an indexer to fetch the historical events.since our pallet haven't had an event just for program logging atm (this is also an option), the current implementation could be sending messages to another program, this PR uses
Actor::zero
as a logger program@gear-tech/dev