-
Notifications
You must be signed in to change notification settings - Fork 7
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: example app and waku_destroy
#99
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.
Very nice thanks!
Would it be useful to store the node config in WakuNodehandle
, only on Running
nodes allow call to waku_destroy
then return an Initialized
node?
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.
LGTM! Very educational PR, thanks for it!
qq: why waku_destroy
is needed? We don't have such concept in nwaku-libwaku
.
@@ -43,6 +43,18 @@ pub fn waku_new(config: Option<WakuNodeConfig>) -> Result<WakuNodeContext> { | |||
} | |||
} | |||
|
|||
pub fn waku_destroy(ctx: &WakuNodeContext) -> Result<()> { |
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.
Maybe it worth adding a little comment above
The reason why it is necessary is because in In waku-org/nwaku#2499 I added the |
Wonderful! Thanks for that! |
f76853b
to
dd0f4fa
Compare
dd0f4fa
to
bafcc76
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## nwaku #99 +/- ##
========================================
Coverage ? 70.00%
========================================
Files ? 11
Lines ? 860
Branches ? 0
========================================
Hits ? 602
Misses ? 258
Partials ? 0 ☔ View full report in Codecov by Sentry. |
No description provided.