- Issue created by @bnjmnm
Currently, when a prop is invalid and that value (or lack of one) is sent to the backend, that component in the preview is replaced with a generic "Component failed to render" message. This seems to be seen as an error that should be avoided at all costs, but it's actually an effective way of conveying that the current value is not an acceptable one.
If it provides a more detailed message regarding the validation problem + styled in a manner that feels more deliberate, this will likely be more useful.
Active
0.0
Page builder