fix: behaviour of group api function #2370
Merged
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.
The function that tells us if we're connected to a group now behaves according to the documentation and returns true if we're attempting to connect to a group, rather than only returning true if we've connected with other peers.
The original purpose of this function was to inform us if we've manually disconnected from a group. In all other instances, we are effectively "connected" in the sense that we're actively searching for the group in the DHT, if not outright connected to other peers.
This change is