Functional Attribute/Prop Node

[nstepien]

Functional Attribute/Prop Node

[nstepien]

I think such functional attributes should always be passed "rendered", they should be never be passed as is like components. So a component can never receive an attribute node, only its rendered value.
Unlike with components, I don't think there is really any value in passing attribute nodes.

For example

function MyComponent() {
  return (
    <ChildComponent
      // passed as is, `ChildComponent` can do `React.cloneElement(props.saveButton, ...)`
      saveButton={<Button {...props} />}
      // the `Disabled` functional attribute is rendered after `MyComponent` is rendered, and before `ChildComponent` is rendered
      disabled={<Disabled />}
    />
  );
}

This would make introducing this feature a non-breaking change.
There wouldn't be any TS/Flow user typings changes to make either, an attribute that expects a boolean can also accept a functional attribute returning a boolean.

[gaearon]

Hi, thanks for your suggestion. RFCs should be submitted as pull requests, not issues. I will close this issue but feel free to resubmit in the PR format.