[Experimental] component as props for IconButton

[Lendemor]

Only accept static component because we still need to define the imports during compilation time.

rx.icon_button(icon=rx.icon(tag="add"))

[masenf]

This is cool! Would it be possible to set a component var in State now?

The private attr in Component makes me a bit nervous, we should add a test to verify that is actually a per-instance value with no bleed over between instances.

[Lendemor]

I did test setting a component as var in the State, sadly it doesn't work, for two reason:

1. Since a var State value will be determined at runtime, we can't find the import that will be needed (they must be written during compilation time.
2. Even when the import is present, the Component set inside the state var is not evaluated correctly.

I don't know if it's definitely impossible or if I'm missing some React knowledge to make it work though.

[ElijahAhianyo]

I did test setting a component as var in the State, sadly it doesn't work, for two reason:

1. Since a var State value will be determined at runtime, we can't find the import that will be needed (they must be written during compilation time.
2. Even when the import is present, the Component set inside the state var is not evaluated correctly.

I don't know if it's definitely impossible or if I'm missing some React knowledge to make it work though.

I havent thought this well through but perhaps we can construct the imports dynamically at runtime using dynamic imports and since we know the component we should be able to extract the import paths. A problem I see may be constructing the JSX

[Lendemor]

I did test setting a component as var in the State, sadly it doesn't work, for two reason:

1. Since a var State value will be determined at runtime, we can't find the import that will be needed (they must be written during compilation time.
2. Even when the import is present, the Component set inside the state var is not evaluated correctly.

I don't know if it's definitely impossible or if I'm missing some React knowledge to make it work though.

I havent thought this well through but perhaps we can construct the imports dynamically at runtime using dynamic imports and since we know the component we should be able to extract the import paths. A problem I see may be constructing the JSX

This might be possible, though I see this as a separate PR later on that we can add.
Constructing dynamic import should not be too hard, but constructing the React component from a state value might be a tad more complicated.

I'm closing this PR since #2124 has the proper implementation of this feature.