Keep the room creation spinner open until the new room is received from server #31311
+3
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…om server In the upcoming work for encrypted state, we need to keep the spinner until the m.room.encryption event is received. This change keeps the spinner just a little longer than before: until the room is received from the server. I'm submitting this change partly because I think it makes sense to delay until we can confirm the room exists and partly to separate this change from other changes that will be involved in encrypted state. That way if this causes problems we can discuss or revert it separately.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In the upcoming work for encrypted state, we need to keep the spinner until the m.room.encryption event is received. This change keeps the spinner just a little longer than before: until the room is received from the server.
I'm submitting this change partly because I think it makes sense to delay until we can confirm the room exists and partly to separate this change from other changes that will be involved in encrypted state. That way if this causes problems we can discuss or revert it separately.