Skip to content

Adding Team and Enterprise to MemberJoinedChannel, and Team to MemberLeftChannel - #273

Merged
soxtoby merged 1 commit into
soxtoby:masterfrom
we4sz:member-channel-event-teams
Nov 1, 2026
Merged

soxtoby merged 1 commit into
soxtoby:masterfrom
we4sz:member-channel-event-teams

Conversation

@we4sz

@we4sz we4sz commented Oct 31, 2026

Copy link
Copy Markdown
Contributor

The reference for member_joined_channel documents team and enterprise, and the one for member_left_channel documents team, but MemberJoinedChannel and MemberLeftChannel have no properties for them, so they only show up in ExtraProperties. They say which workspace and org a person who joined or left a channel is from. I found them comparing the reference pages of the events my app subscribes to with their SlackNet classes. This models them. It is one commit.

  1. MemberJoinedChannel.Team (team): "Team ID, identifying which workspace the user is from." and Enterprise (enterprise): "Enterprise ID, identifying which org the user is from. The value will be blank if the user's team is not an Enterprise organization."
  2. MemberLeftChannel.Team (team), with the same description as on the joined event.

Compatibility

Additive only, but like #264 it moves fields: code that reads team or enterprise out of ExtraProperties on these two events stops finding them there.

Testing

New MemberChannelEventTests: the joined event with both fields (the payload from the reference, which also checks that nothing is left in ExtraProperties), one without them, and the left event with team. ./do test passes (786 tests).

Not verified: I haven't captured either event from a live workspace, so these follow the reference pages and their examples only. My app subscribes to both events and doesn't use these fields today.

@soxtoby
soxtoby merged commit 898a339 into soxtoby:master Nov 1, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants