-
Notifications
You must be signed in to change notification settings - Fork 2
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
WIP feature/TypingIndicator extracted and usable as seperate component #49
base: master
Are you sure you want to change the base?
WIP feature/TypingIndicator extracted and usable as seperate component #49
Conversation
typingIndicatorContent: @Composable ColumnScope.(List<TypingUi>) -> Unit = { typing -> | ||
TypingIndicatorContent(typing) | ||
}, | ||
typingIndicator: @Composable () -> Unit = { TypingIndicator() }, |
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.
Should still use ColumnScope
to allow custom modifications based on root layout
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.
The name should stay too. typingIndicator
suggest that the instance of indicator will be passed.
} | ||
) { | ||
Column { | ||
checkNotNull(LocalChannel.current) |
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.
channel
can be extracted as a parameter to allow passing channelId to component
I think that the feature is invalid. The criteria change the uniform way of transferring data to components. The topic was also not discussed with other teams to maintain similar behavior. IMHO should be rejected. |
Can we close this PR? |
No description provided.