What's the difference between functionalComponent() and rFunction()?

# react

[Big Chungus]

What's the difference between functionalComponent() and rFunction()?

[andylamax]

I think on returns an RClass while another returns a ReactElement . But they work and behave the same

[Big Chungus]

Why would anyone use functionalComponent() over rFunction()??

// given
val A = functionalComponent<RProps>() {}
val B = rFunction<RProps>("B") {}

// usage
fun RBuilder.render() {
  child(A) {
    attrs {
      ...
    }
  }
  B {
    attrs {
      ...
    }
  }
}

B seems to be much easier to use and read...

[andylamax]

Interop reasons. Some methods would require you to pass or return an ReactElement (i.e. buildElement) and some methods need to you to pass or return RClass i.e. (RBuilder.child(el: RClass)). Use one or the other whenever you need em

[Akif Abasov [JB]]

They are same. Just legacy that should be solved. I’ve added functionalComponent with adding hooks to wrappers because didn’t noticed that there’s rFunction that is functional component.

[Akif Abasov [JB]]

Now i think that best naming is rComponent to be similar with RComponent class. But there already are rFunction and functionalComponent , it think that i should deprecate rFunction and then remove it as less obvious and discoverable naming.

[Big Chungus]

I personaly prefer rFunction over functionalComponent because its usage is less verbose

[Akif Abasov [JB]]

what about rComponent ?

[Big Chungus]

A bit too ambiguous, don;t you think? Since Component can be either functional or class-based

[Big Chungus]

But don't mind it all that hard

[turansky]

+1 for rComponent