-
Notifications
You must be signed in to change notification settings - Fork 16
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
chore: Review fixes #458
base: feat/replies
Are you sure you want to change the base?
chore: Review fixes #458
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## feat/replies #458 +/- ##
================================================
- Coverage 72.37% 72.12% -0.26%
================================================
Files 63 63
Lines 3823 3860 +37
================================================
+ Hits 2767 2784 +17
- Misses 1056 1076 +20 ☔ View full report in Codecov by Sentry. |
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.
It's good to have that check. There are some more examples to be checked as well
@@ -11,7 +11,36 @@ use crate::types::msg_field::MsgField; | |||
use crate::types::msg_variant::{MsgVariant, MsgVariants}; | |||
use crate::utils::emit_turbofish; | |||
|
|||
const NUMBER_OF_DATA_FIELDS: usize = 1; | |||
const NO_ALLOWED_DATA_FIELDS: usize = 1; |
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
stands for number here? If so it's quite misleading in this context
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.
ye, number of. It is a bit if you don't check the type. I will revert this change.
fn first_reply( | ||
&self, | ||
_ctx: ReplyCtx, | ||
#[sv::data(opt, raw)] _data: Option<Binary>, |
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.
Let's add few more combinations:
- What would happen if there is an additional argument before
sv::data
? - What happen if we use
#[sv::data(opt, raw)]
onctx: ReplyCtx
? - What happen if we use
#[sv::payload(raw)]
onctx: ReplyCtx
? - What if we skip
ctx: ReplyCtx
? - Can we use
#[sv::data(raw)]
after#[sv::payload(raw)]
?
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.
- Missing payload parameter. - This might cause some weird behavior due to deserialization to empty tuple.
Good points.
For 2 and 3 nothing would happen as context types are skipped during parsing.
For 4 as in case of every message type it would fail with Rust compile error that context types couldn't be converted to whatever parameter is defined first. We are unable to check if the second parameter in the method signature is ReplyCtx
as this would make usage of aliases impossible or very restricted and in the end wrong type could still be passed there.
Added test cases for the rest.
No description provided.