Question about passing props when using Kotlin/JS & React. When you create an element using ``` ...

# javascript

[Don Kittle]

Question about passing props when using Kotlin/JS & React. When you create an element using

element = About.create()

How does one go about passing props to the element on creation?

[turansky]

element = About.create {
    // your props
}

[Don Kittle]

Thanks!

[Don Kittle]

Hmm, I must be missing something obvious. The prop is undefined in the child component. This is my parent component. The log statement prints out the webUser's properties.

Route {
   path = "/campaigns"
   element = Campaigns.create {
      webUser
   }
   console.log("web user ->>> $webUser")
}

[Don Kittle]

My child is set up like this and webUser is undefined....

external interface CampaignWebUserProps: Props {
    var webUser: WebUser
}

val Campaigns = FC<CampaignWebUserProps> {props ->

    val webUser by useState(props.webUser)
...
}

[Don Kittle]

Am I missing something obvious?

[turansky]

element = Campaigns.create {
    this.webUser = webUser
}

[turansky]

If user data is common - it’s preferrable to use React Context instead

[Don Kittle]

AHHHH, thanks so much! That works 🙂

[Don Kittle]

Ok, I'll read up on Context right now

[Don Kittle]

I also just realize I can handle "injecting" bearer and dealing with refresh automagically with Ktor client so I won't need to do this (above) much longer. But I'm sure I'll want to pass props from parent to child sometime.

[turansky]

Components, which I use for routes have no props.
With Context you avoid redundant rendering for components, which don’t use data directly (for proxies)

[turansky]

In next version it will be possible to use ComponentType instead