Federico Bonel Tozzi

Hey @kuntlme! Feel free to open a PR 🙏 Just a quick reminder: - Slots are not visible by default - Every field has a `visible` config parameter that can...

Awesome! Also, I almost forgot, in case you haven’t already, make sure to give [this](https://github.com/puckeditor/puck/blob/main/CONTRIBUTING.md) a quick skim so you’re familiar with how we typically handle contributions.

After further inspection today, I realized this is happening because the padding is applied to the [individual field wrapper](https://github.com/puckeditor/puck/blob/ace4c8b354107b8bf7b4cd54a3924911f23beb10/packages/core/components/Puck/components/Fields/index.tsx#L137). Given that, I think the best solution would be to introduce...

Hey @SlawomirMazgaj! Thanks for reporting this. I initially thought it was a bug, but it turns out this is actually intended behavior with actions, since they’re meant to be atomic....

Hey @SlawomirMazgaj! Yes, the data you would pass is the `appState.data`, which represents your entire editor data. > I think in my specific use case I don't have any async...

Another issue with the permissions docs is that we don’t fully document which permissions are supported at each level. This could also be a problem with the permissions types, since...

Applied the requested changes, only need to go through the commit history to fix it up with you!

I spun off adding the `parent` prop to `resolveData` into its own issue since it's a prerequisite. Tracking here: #1359

Hey @ojj1123! No, it won't be deprecated. It's a very important part of the Puck API for React Server Components and overall usage. This refers to some parameters that `resolveAllData`...

We should probably mark `onResolveStart` and `onResolveEnd` as deprecated to give people time to migrate before removing them.