andylamax
09/04/2021, 11:20 AMkotlin-react.
A lot of things are now very consistent.
Follow question though. I see that we have
interface RBuilder {
// . . .
fun <P : Props> child(
klazz: KClass<out Component<P, *>>,
handler: RHandler<P>,
)
// . . .
}
Question is, why don't we have
interface RBuilder {
// . . .
fun <P : Props> child(
klazz: KClass<out Component<P, *>>,
props: P,
handler: RHandler<P>,
)
// . . .
}
So that I may
child(Hellow::class,jsObject{
param1 = 1
param2 = 2
param3 = "three"
// . . .
})
instead of
child(Hellow::class) {
attrs {
param1 = 1
param2 = 2
param3 = "three"
}
}
turansky
09/04/2021, 11:54 AMchild
methods, invoke
preferred
• Remove class component specific methods (as non-flexible)
cc @Sergei Grishchenkoturansky
09/04/2021, 11:55 AMandylamax
09/04/2021, 4:11 PMturansky
09/04/2021, 5:01 PMHellow {
param1 = 1
param2 = 2
param3 = "three"
}
without attrs
block, without RBuilder
🙂
Already works in draftturansky
09/04/2021, 5:02 PMKClass
- blocker for effective/minimalistic APIandylamax
09/05/2021, 6:32 AMandylamax
09/05/2021, 6:33 AMturansky
09/05/2021, 1:26 PMandylamax
09/05/2021, 6:31 PMturansky
09/05/2021, 8:17 PMandylamax
09/06/2021, 3:11 AMval Profile by fc<Props> { . . . }
andylamax
09/06/2021, 3:12 AMturansky
09/06/2021, 5:02 AMandylamax
09/08/2021, 1:23 AMturansky
09/08/2021, 1:58 AMturansky
09/08/2021, 1:59 AMattrs
turansky
09/08/2021, 2:01 AMturansky
09/08/2021, 2:03 AMActionButton {
label = "OK"
onClick = props.onNext
}
Future main syntax 🙂andylamax
09/08/2021, 2:46 AMandylamax
09/08/2021, 2:46 AMandylamax
09/08/2021, 2:48 AMturansky
09/08/2021, 4:42 AMandylamax
09/08/2021, 8:43 AM