You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 19, 2022. It is now read-only.
Switch element exposes input properties as INPUT.() -> Unit, while TextField exposes them as InputElementBuilder<InputProps>.() -> Unit. The resulting code looks different for different elements which does not look good. It seems like Switch way is preferable.
Actually, these two lines:
varTag.InputProps:RProps? by materialProps
varTag.inputProps:RProps? by materialProps
look really uncomfortable.
The text was updated successfully, but these errors were encountered:
It seems like this one is a problem of Material-UI, not the wrapper. Still, for those not familiar with it, it is really confusing. I think that the difference should be documented.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Switch element exposes input properties as
INPUT.() -> Unit
, while TextField exposes them asInputElementBuilder<InputProps>.() -> Unit
. The resulting code looks different for different elements which does not look good. It seems like Switch way is preferable.Actually, these two lines:
look really uncomfortable.
The text was updated successfully, but these errors were encountered: