-
Notifications
You must be signed in to change notification settings - Fork 7
feat: allow manager to interact with different rav and receipt #259
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
Signed-off-by: Gustavo Inacio <[email protected]>
28baab5 to
6885d9c
Compare
Pull Request Test Coverage Report for Build 12915395703Details
💛 - Coveralls |
Signed-off-by: Gustavo Inacio <[email protected]>
54a065d to
07fa2d8
Compare
refactor: remove unused escrow handler Signed-off-by: Gustavo Inacio <[email protected]>
Signed-off-by: Gustavo Inacio <[email protected]>
9ad810d to
44f0afa
Compare
|
|
||
| [dependencies] | ||
| tap_core = { path = "../tap_core", version = "2.0.0" } | ||
| tap_core = { path = "../tap_core", version = "2.0.0", features = ["test"] } |
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.
Not really liking this feature here in tap_aggregator
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.
Yeah... Why is it required?
| use criterion::{black_box, criterion_group, criterion_main, Criterion}; | ||
| use tap_core::{ | ||
| rav::ReceiptAggregateVoucher, receipt::Receipt, signed_message::EIP712SignedMessage, | ||
| rav::{Aggregate, ReceiptAggregateVoucher}, |
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.
Are these benchmarks used?
| received_rav: ReceiptAggregateVoucher, | ||
| expected_rav: ReceiptAggregateVoucher, | ||
| received_rav: String, | ||
| expected_rav: String, |
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.
This seems strange! This is to allow for basically any generic message? Why not use a newtype?
| }, | ||
|
|
||
| /// Error when the received RAV does not match the expected RAV | ||
| #[error("Received RAV does not match expexted RAV")] |
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.
| #[error("Received RAV does not match expexted RAV")] | |
| #[error("Received RAV does not match expected RAV")] |
| #[cfg(any(test, feature = "test"))] | ||
| impl From<crate::receipt::SignedReceipt> | ||
| for ReceiptWithState<Checked, crate::receipt::SignedReceipt> | ||
| { | ||
| fn from(signed_receipt: crate::receipt::SignedReceipt) -> Self { | ||
| ReceiptWithState { | ||
| signed_receipt, | ||
| _state: Checked, |
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 see
| } | ||
| } | ||
|
|
||
| let receipts = receipts.into_iter().map(Into::into).collect::<Vec<_>>(); |
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.
No big deal but here is one place I'd like to see what type it's being coerced to 😄
This PR: