Federico Bonel Tozzi

Hey @benlife5! Thanks for opening this issue and reporting the bug. I can confirm that I can reproduce this with Puck `0.20.2`. Interestingly this doesn't happen if the paste target...

The issue tracking the move up overlay rendering problem is this one: #955

Following this up with the last action we set up from the previous PR: > Hey @OsamuBlack sorry for the delay! I think this PR has the right bones, but...

Not on your end @OsamuBlack! Thanks again for the contribution, we just need to fix the overlay not moving bug and the UX

Hey @OsamuBlack! Thanks for the contribution 🙏. Just a quick heads-up: the issue is still marked as in triage. That means it’s not fully ready for implementation yet, and it...

Hey @1benw! Interesting! I do wonder if it might be better to provide a separate prop for this, since `metadata`, at least to me, feels tied to the Puck data...

Thanks for requesting this feature! Here are the related Discord discussions about it: - https://discord.com/channels/1153376562259951687/1409434446624456754 - https://discord.com/channels/1153376562259951687/1404778308058746951 - https://discord.com/channels/1153376562259951687/1374476753258676244 - https://discord.com/channels/1153376562259951687/1424858872706764942/1425227893365276696 I think adding an additional prop might work to...

This recently came up again in a [use case where they needed to synchronize props across multiple nested components in different slots](https://discord.com/channels/1153376562259951687/1424858872706764942/1425227893365276696). To handle this, they used context and effects...

Since many of these proposals would require some component search functionality, this might also be related to #186.

Awesome idea, thanks @renenielsendk!