Skip to content

chore: refactor nwaku.go to avoid repeated function calling pattern #80

@gabrielmer

Description

@gabrielmer

There's a clear pattern in all the functions in nwaku.go which call libwaku functions.

We should encapsulate the shared logic in a function so we avoid duplicated code.

Attached are a couple examples of how the refactored version could look like

example_1.txt
example_2.txt

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions