Taylor Vann

I'm thinking the react wrapper API would feel like: ``` export const MyElementComponent = createComponent( React, 'my-element', MyElement, // events { onChange: 'input', }, // children { propName: 'slot_name', icons:...

@sorvell Another cheap solution might just be to set children into a `fragment` or `` that has a `slot` property. Would be relatively easy to map this ourselves. ``` ()...

@bugwheels94 I agree

@justinfagnani I also agree! css is kinda cool sometimes!

I have a hunch that using the minimum shared interface between React and Preact could alleviate this. There's a lot in React that is not included in Preact so the...

Hey @ashleyryan @mjaggard! We have updates! We've updated how we apply react props onto web components inside the wrapper. Properties like `hidden` and `id` should now be handled correctly for...

Want to confirm that boolean properties like `hidden` work as expected in the wrapper. However there are other attributes which are not boolean that take boolean values like `id`. In...

@ashleyryan All but one test? I'll take that hahah nice :) Very curious about the last test. The fact that it passed most of y'alls tests is really encouraging.

Thanks so much @ashleyryan for the extra help, I really appreciate it. Im going to mark this issue as resolved from #3128

Hey @michaelwarren1106! There have been some updates. I think some of our tests match your use case. We declare the web component in the `HTMLElmenetTagNameMap` and the `IntrinsicElements` namespaces. https://github.com/lit/lit/blob/main/packages/labs/react/src/test/create-component_test.tsx#L20-L31...