Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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: enable event emission for peer discovery/connection in ConnectionManager #1438
feat: enable event emission for peer discovery/connection in ConnectionManager #1438
Changes from 18 commits
95715d4
34e22ad
164508c
1e0708b
dfa3618
da6b661
b815615
15a9484
fb8ae26
a32e9de
5c6074c
82b9239
81539c2
fc07c9a
9e6aece
dae61fa
9d28213
ba03bc3
9d777c9
81c2544
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I guess we can optimize here and just
getConnections
which returns tags as well so that later there is no reason to await for peer storeThere 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.
correct. that is a more efficient way, agreed.
related comment: #1438 (comment)
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.
you don't need to use
getTagNamesForPeer
but you can directly refer topeer.tags.keys()
to avoid async operationThere 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.
it is done to keep fetching tags consistent through this function; agreed that it is async, but it is computationally low demand so should be ok
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.
I am wondering what is the difference if the same
tags
are present onpeer
in the loop as well as those you'd get fromthis.getTagNamesForPeer
?