Better handling of JOIN/PART events. #76
Open
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.
PART
s a Slack channel (even though the state does not update on the Slack side), we can allow the client to re-join a channel (once) without having to reconnect. Previously there was no way to re-join a channel you left on an IRC client (we would never send theJOIN
echo since we checked joined channels against Slack).channel_joined
andchannel_left
. This information was duplicated bymember_joined_channel
andmember_left_channel
, with the sole exception of channel archiving, which does not generatemember_left_channel
. We now ignore themember_*
variant for the self user.chan interface{}
andmap[x]interface{}
withstruct{}
lmbo.