You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support for this syntax would be helpful for ReasonReact:
<div {...props} />
Conceptually it maps to a component whose total set of props has been created elsewhere. I'd propose that it could desugar to:
let _ = ((div props)[@JSX ])
Importantly - I don't think that it's useful or interesting (for the purposes of ReasonReact at least) to support props spread+individual props. I am not asking for support for either of:
For context on why I want this - today RR components are a set of two functions - x and xProps in the same module scope. Sometimes folks want to (or can only) make a component which is just x. This syntax allows them to do so and get the props through any means that they'd like while still being able to use JSX.
The text was updated successfully, but these errors were encountered:
Support for this syntax would be helpful for ReasonReact:
<div {...props} />
Conceptually it maps to a component whose total set of props has been created elsewhere. I'd propose that it could desugar to:
Importantly - I don't think that it's useful or interesting (for the purposes of ReasonReact at least) to support props spread+individual props. I am not asking for support for either of:
For context on why I want this - today RR components are a set of two functions -
x
andxProps
in the same module scope. Sometimes folks want to (or can only) make a component which is justx
. This syntax allows them to do so and get the props through any means that they'd like while still being able to use JSX.The text was updated successfully, but these errors were encountered: