-
Notifications
You must be signed in to change notification settings - Fork 42
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
waku relay API: auto-subscribe #17
Comments
Let's wait until waku-org/nwaku#445 is resolved before trying to tackle this one as we know of some timing issues and there would be little value if we have various |
This is an issue more for library design, is that correct? In terms of making it ergonomic and having to setup fewer things for the default behavior. |
yes correct, I use the label 'API' to flag anything which is more about the API itself, the dev ex using it and any issue/improvements that can be done on its current design. This is low priority as the focus is to get the chat app to support waku store first. |
At this stage, if waku relay is mounted then we always want to subscribe to default topic. We can re-introduce the flexibility once we know what matters to the user. Resolves #17.
At this stage, if waku relay is mounted then we always want to subscribe to default topic. We can re-introduce the flexibility once we know what matters to the user. Resolves #17.
Problem
Currently, developer always need to do a call to
WakuRelay.subscribe()
to use waku relay.Solution
Similarly to nim-waku, an auto-subscribe to the default topic can make the API easier to use as the developer would have one less call to do.
The text was updated successfully, but these errors were encountered: