validateDOMNesting one is worth fixing, as it may break hydration, but you can ignore the setControlContextData one, as that won’t be there in production
So how do we fix validateDOMNesting ?
In the rendered page, you can find the offending element with document.querySelector("p div"), and then identify what component it came from and fix it in the studio
Oooh! You mean like this in console CLI… As I see null:
hmm that’s on the same page that was showing the validateDOMNesting error?
