fix(phoenix-channel): queue join
message before others
#4242
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.
This was discovered as part of #4213. When we reconnect to the portal, we first need to join the correct room before sending any messages to it. For example, as a client, we need to join the
client
room before sending messages in it.This implementation is meant to be a quick fix. The "proper" solution would be to keep track of which rooms we have joined and reset that upon reconnect. Introducing such a state machine is a much larger refactoring that is likely not going to make much of a difference for now because we only join a fixed number of rooms and that will usually succeed.