-
Notifications
You must be signed in to change notification settings - Fork 768
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Room setting: improve room history and add join rule #2458
Conversation
a76ca6a
to
b94d682
Compare
And observe correctly the state event
Including a reusable bottom sheet pattern, for future join rules setting bottom sheet
b94d682
to
c785ea6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just one small remark. Thanks for the generic bottomsheet
return taskExecutor.executorScope.launchToCallback(coroutineDispatchers.main, callback) { | ||
if (joinRules != null) { | ||
awaitCallback<Unit> { | ||
sendStateEvent( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe create a private suspend sendStateEvent to avoid passing twice from callback to coroutine
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the remark. This will be reworked when migrating this service API to coroutines.
Fixes #2442 and last part of #1579
This PR also fix some issue about the wording.
This PR introduces some parent classes to quickly implement a bottom sheet to make a choice between several possibilities.
Screenshot of the change