refactor framing_sv2 example
#1468
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1468 +/- ##
==========================================
+ Coverage 18.28% 18.85% +0.56%
==========================================
Files 127 116 -11
Lines 9738 8758 -980
==========================================
- Hits 1781 1651 -130
+ Misses 7957 7107 -850
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
plebhash
force-pushed
the
refactor-framing-sv2-example
branch
5 times, most recently
from
7d24f3f to
52e824f
Compare
plebhash
changed the title
framing_sv2 exampleframing_sv2 example
nice catch, we didn't but I just added a commit that runs it from |
Should we also add other examples that we recently included during our documentation efforts, since not all of them have been added to CI? |
|
|
||
| // Example message type (e.g., SetupConnection) | ||
| const MSG_TYPE: u8 = 1; | ||
| // Example extension type (e.g., a standard Sv2 message) | ||
| const EXT_TYPE: u16 = 0x0001; | ||
|
|
||
| #[derive(Serialize, Debug)] | ||
| #[derive(Serialize, Deserialize, Debug, Clone)] | ||
| pub struct CustomMessage { |
There was a problem hiding this comment.
thinking out loud here, wouldn't it be more beneficial to actually have an SV2 message here? for the MSG_TYPE, SETUP_CONNECTION is used, maybe here as well?
we need to assert that the deserialized message has the same content from the original
plebhash
force-pushed
the
refactor-framing-sv2-example
branch
from
cd6226b to
cb2b67b
Compare
|
This should be good to go now? cc: @plebhash |
close #1467