Suraj Air
Suraj Air
Yes. Same here. onMove is giving incorrect position. at root level, if there are two nodes, it am getting position as 2 whereas it should have been 1.
> Possible solution? instead of get the index from the args in onMove, yo can get the proper one from the tree state like this, where tree is the ref...
@AliGhaleyan this is a good idea. We should pass a component instead of a ReactNode. Passing a component will allow use to render the component in context of the app....
Close and resolve this in a separate PR
hi, Do you mean integrating ui library like Sera UI, or other Tailwind based libraries?
hi, we are launching our registery similar to shadcn ui. So you should be able to add blocks directly from our registery and also create your own
Removing `--turbopack` in 15.6.7 worked for me