-
Notifications
You must be signed in to change notification settings - Fork 125
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
Add Encode Decode to ExtrsinicReport and use RawExtrinsicDetails #704
Conversation
95f745f
to
fccc026
Compare
remove error changes and fix build clean up add transforming functions remove non-consuming function add comment add encode decode to extrinsicreport impl same functions for both event details and raw event details fix lifetime add metadata check fix clippy use raw events in extrinsic report fix tests one more fix :)
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.
Since the reason for this change, is that we want to support serialization/deserialization, I would add a test for that. Then we know this capability will not be removed without a failing test.
Apart from that it looks good to me
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.
After our discussion, I'd say it's good now
EventDetails
as they do not implement codec Decoding / Encoding.RawEventDetails
to allow usage of EventDetails without always holding the full metadataExtrinsicReport
to useRawEventDetails
instead, to make the report smaller. Otherwise, the full metadata would get encoded / decode and moved all the time. I'd rather keep the report small. If needed, one can always transform theRawEventDetails
back toEventDetails
closes #397