includeAll() includes first layer of nested children objects, not multiple

[TravisDev]

New Issue Checklist

• [x ] I am not disclosing a vulnerability.
• [ x] I am not just asking a question.
• [ x] I have searched through existing issues.
• [x ] I can reproduce the issue with the latest versions of Parse Server and the Parse JS SDK.

Issue Description

When using the method in the SDK Parse.Query.includeAll()... It will include all of the objects that are directly nested, but will not include nested objects in the nested objects.

Steps to reproduce

create a nested object Parent { child { grandchild {}}}... Query parent.get(id) includeAll(), you will not get all fields. remove the includeAll() and replafce it with include("child") and include("child.grandchild") and it will work as intended.

Actual Outcome

using includeAll, you can see basic data of the object, but no custom fields.

Expected Outcome

includeAll should include all of not just the child, but grandchild, greatgrandchild, etc...

Environment

Server
docker container parseplatform/parse-server:latest

Database
docker container mongo:latest

Client

• Parse JS SDK version: 2.15.0

[dplewis]

This is the expected behavior. This uses the _SCHEMA class to get the name of the nested / pointer fields. The _SCHEMA as no way of knowing what multiple layers are.

[TravisDev]

@dplewis Gotcha. I was looking at it and was unsure. Is is practical to implement this usuing something other than _SCHEMA or in conjunction of something else to be able to find the multiple layers? I would be interested in contributing this if you believe it is feasible.

[dplewis]

its doable but we would have to think about what all means. It could be n levels deep and we would have to check for recursion. It might be inefficient and costly query too