Skip to content

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

Closed
dannywolfmx opened this issue Feb 11, 2019 · 4 comments · Fixed by #1223
Closed

The dashboard does not work well with nested objects #983

dannywolfmx opened this issue Feb 11, 2019 · 4 comments · Fixed by #1223

Comments

@dannywolfmx
Copy link

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

[
    {
        "text": "Hello",
        "myPointerObject": {
            "__type": "Pointer",
            "className": "Producto",
            "objectId": "K4vUSfxkMx"
        }
    }

]

And parse dashboard made the next evaluation:

Bad formed array with nested object

[
    {
        "text": "Hello",
        "myPointerObject":{
            "objectId": "K4vUSfxkMx"
        }
    }

]

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.

@masonlee
Copy link

masonlee commented Mar 12, 2019

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.

@dannywolfmx
Copy link
Author

Hi, I already made a PR solving the issue, but is still waiting to revision.

@stale
Copy link

stale bot commented May 4, 2019

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.

@stale stale bot added the state:wont-fix Won’t be fixed with a clearly stated reason label May 4, 2019
@stale stale bot closed this as completed May 11, 2019
@douglasmuraoka
Copy link
Contributor

@dplewis can't we just render and edit the array/object just as it was stored in the database?
It sounds like a mistake to handle Parse.Objects inside the generic array/object, since, well... that's generic and could store anything.

@stale stale bot removed state:wont-fix Won’t be fixed with a clearly stated reason labels Aug 13, 2019
douglasmuraoka added a commit to douglasmuraoka/parse-dashboard that referenced this issue Aug 14, 2019
…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.
dplewis pushed a commit that referenced this issue Aug 15, 2019
…t fields (#1223)

Fixes #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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants