-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
The dashboard does not work well with nested objects #983
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
Comments
I am running into this same issue. It looks like the Parse Dashboard is somehow making "__type" and "className" properties invisible. They are present in the mongodb entry. |
Hi, I already made a PR solving the issue, but is still waiting to revision. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@dplewis can't we just render and edit the array/object just as it was stored in the database? |
…t fields Fixes parse-community#983 When rendering/editing `Array` or `Object` type fields on `Database Browser`, we must avoid any transformations of generic data to the `ParseObject` format. Since these fields are generic, we can't assume it will contain Parse related content.
Hi.
I have the next issue:
When I save a list of generic objects and one of their children is a Parse.Pointer the dashboard does not interpret it well
Example
Original array with nested object
And parse dashboard made the next evaluation:
Bad formed array with nested object
The problem comes when you try to see the whole json, and the auto-save sistema of dashboard overwrite the original object to the bad formed.
I already fix the issue in the parse dashboard code, tomorrow i will make a PR with the solution.
The text was updated successfully, but these errors were encountered: