3 ms·
No it totally works, it's not bad. The one big broken thing in August was that the type for components (RenderContext) thought component props should be passed
by gavinray 6y ago
No it totally works, it's not bad. The one big broken thing in August was that the type for components (RenderContext) thought component props should be passed as "props={ myprop: 1 }" instead of "myprop={1}".
See:
https://cdn.discordapp.com/attachments/568037134968160256/730811100815163452/unknown.png https://cdn.discordapp.com/attachments/568037134968160256/73...
Comment I made about this I dug up:
"The issue seems to be that the definition for RenderContext<Props> puts the props under the key "props", so when trying to define them on your JSX/TSX element, it expects you to put them under <MyComponent props={ } />. If you do this though, it breaks in another way because it's missing the other properties of RenderContext and it's not a great API =/"
This is fixed now though I am pretty sure.