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
First off, Puck is an incredible library. It's really well thought out and has a beautiful API. Thank you so much for putting this out into the world. 🙏
I'm having issues using the DropZone component with our in-house component library. Here's an example codesandbox of the setup:
We're trying to nest a two levels deep using the DropZone component: ComponentA > ComponentB > ComponentC.
This works great in the sandbox above. However, when we use our in-house "ComponentB" component, we can no longer drop a "ComponentC" onto it.
import{ComponentB}from'@internal/components';constconfig={components: {ComponentB: {fields: {},defaultProps: {},render: ()=>{return(<ComponentB> // if we change this to a div it works fine.
<DropZonezone="component-b"/></ComponentB>);},},//... other components},};
Are there any common pitfalls that we need to check for in our ComponentB?
The text was updated successfully, but these errors were encountered:
Hi there,
First off, Puck is an incredible library. It's really well thought out and has a beautiful API. Thank you so much for putting this out into the world. 🙏
I'm having issues using the DropZone component with our in-house component library. Here's an example codesandbox of the setup:
https://codesandbox.io/p/sandbox/4fpn9f?file=%2Fsrc%2FEditor.tsx
We're trying to nest a two levels deep using the DropZone component: ComponentA > ComponentB > ComponentC.
This works great in the sandbox above. However, when we use our in-house "ComponentB" component, we can no longer drop a "ComponentC" onto it.
Are there any common pitfalls that we need to check for in our ComponentB?
The text was updated successfully, but these errors were encountered: