-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[+] Forms - Embedded arrays containing "deep" embedded documents are json inputs #115
Comments
Hi @Listu, we'll look at your issue next week! |
Hey @Listu we were wondering if you could give us a sample of data you had in your database. A Society document with the embedded members. Thanks ! |
Of course @root-io `
} |
Hi @Listu, this is currently a limitation of our platform. In the case of arrays of embedded document that contain only keys/values with a "single depth level", these arrays will appear in the "Related Data" section. For more complex documents in embedded arrays, as the edition may be very complex, we display a JSON field to manipulate the data. This is clearly not an ideal usage, but at least you can read and manipulate the data. We definitely need to work on this. |
Ok so we have to change our model, wait an improvement or dev our own dashboard. Thank you for the help. |
Any news on this ? |
We have the same problem over here. Flattening all the models could annoying, especially if you are actually modeling a tree structure, i.e. "Project" containing an array of "Sections", containing an array of "Tasks". This is one of the greatest advantages of NoSql - you can simply load the document with Robo3t or other clients, load the document, and see the tree-structure without needing to write code for populating all the arrays of references. |
Expected behavior
Display array of embedded documents as related data
Actual behavior
Displayed as json in the parent document
Context
I have a Society with an array of Member embedded. Members are displayed in "details" and not in Related Data. I tried to create a fake field as a workaround with:
{ field: '_members', type: ['String'], reference: 'Society.members' }
but it try to display societies (whereas I guessed the model put in Liana.ResourceSerializer(Liana, Member... would say to forest "hey it's a Member")
The text was updated successfully, but these errors were encountered: