-
Notifications
You must be signed in to change notification settings - Fork 41
Add Array support as root and nested Fields #132
Comments
@AleksejDix can you provide a code example of what what you're suggesting? |
i was looking at different solution which have a default support for JSON Schema |
Oh, ok JSON Schema I understand now. This has been on the development map for a while now, it would have to be developed as a plugin similarly to what lookup is doing. I don't have the time to do this right now, but will mark the idea as a good enhancement in case anyone wants to take a crack at it :) |
@marina-mosti i think he means this https://vueformulate.com/guide/inputs/types/group/ so basically a repeatable nested schema Or at least i would be interested in this type |
Hey @digitalkaoz building a plug-in to support json schema is not a small undertaking, and currently I have some other things that I want to prioritize. If anyone in the community wants to take it on, that would be awesome and it would be a great opportunity for a first 3rd part plug-in. As for grouping fields, I'm cooking up a solution to be able to create form sections. But if it's a logical separation and not semantic you should be able to achieve it with nested schemas |
Sure, json Schema is a big Task! I would be glad for some Idea on repeatable nested schemas :) |
Can you go ahead and open a discussion about that? I don't want to bloat this issue with a side topic :) |
JSON root type could be any primitive type like Object, Array, String, Boolean, Null and Numbers
Objects and Arrays are most common one for making forms.
Describe the solution you'd like
root Model Value should be able to handle both types Objects and Arrays.
Arrays must hold the same type and it should be possible to repeat the types.
Arrays Entries can be deleted, created and updated.
Array Types can hold any type.
Describe alternatives you've considered
Support All JSON root types.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: