-
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
update connectionManager.dispatchEvent test to listen to correct events #1835
Comments
That's a good catch. I think to simplify everything we should expose and use only waku.dispatch // <- internal only
waku.addEventListener and it will be the same as waku.libp2p.* |
@fbarbu15 can you elaborate? |
Sure, my aim was to increase test coverage for |
@fbarbu15 upon investigating this, I realise that the test case added isn't the right use of the API, thus making this issue not be a bug but an intended behaviour. Let me explain: Let me draw two scenarios which would be right for this:
I propose to update this issue description (since this isn't a bug) and change it into an enhancement where we refactor the existing test case & add the above two cases instead. Moving this to triage while we reach a conclusion & update the issue description. |
You are correct, now that you explained it, it makes total sense, thank you! |
resolved by #1897 |
This is a change request
Problem
Update test according to comment
The text was updated successfully, but these errors were encountered: