Closed christiancode14 closed 1 year ago
Hi, @christiancode14, thanks for reporting your issue!
Indeed, the v-editable
is only meant to be used in the blok
since it is used to connect the FE component instance with the corresponding block inside the SB visual editor. What are you trying to achieve by using it outside a component? Just in case I can guide you towards the solution.
Only one thing, next time, use the SDK bug report template to help us have a clear understanding of your issue, thanks in advance for that <3
Thanks for your reply and sorry for using the wrong template ;)
In this case we're trying to minimize flexibility/room for error for our client. We want them to fill out the content by a certain structure which means we don't want to use the Blok fields for certain elements. Instead we're using grouped fields. Now, whenever the client clicks on a title in the visual editor I'd like the input to be focused so the client knows what to fill in. But unfortunately this only works with fields inside Bloks.
Thanks, @christiancode14, for letting me know your use case. I will create a Feature Request internally since it is such a nice idea and could be helpful for other users! Are you a developer from a Partner? Just to let my team know from where is coming 💜
Thanks! That would be great! Yes, I'm from CODE14
I don't know if it is even possible, but I'm trying to add the v-editable directive to non-blok fields. I can see the dashed outline on the component but whenever I click it it gives the following console error:
Is it even possible to use the v-editable directive without Bloks?