resolveData on root about puck HOT 3 CLOSED

Hi @joaojoyce! Thanks for your report, but unfortunately I'm unable to reproduce. I tried copying your code snippet above into the demo application and the resolver ran fine.

If you can share a repo or codepen which reproduces the issue, I can investigate further.

from puck.

Hi @chrisvxd ,

I found out that resolveData doesn't work if I pass properties to <Puck />. I also get the warning that passing properties to <Puck /> is deprecated.

So this does work:

<Puck config={config} />

This doesn't

<Puck 
          overrides={{headerActions:()=>(...)}}
          onChange={(data) => {onChange({ target: {  name, value: JSON.stringify(data)}})}} 
          data={initialData} config={config}  >
</Puck>

Is this intended? It's very convenient and intuitive to pass these properties to puck directly. Also, this makes it easy to abstract generic configs that would work the same on <Puck /> and on <Render />.

For instance, the onChange and overrides that I have here aren't needed on my frontend where I render...

from puck.

Nevermind. It was my initialData that was not built correctly.

from puck.