使用承诺时在 Parse Cloud Code 中返回更深层次的关系

Returning deeper relations in Parse Cloud Code when using promises

到目前为止,我已经收到了一些关于 Parse promises 的优秀信息,并准备好解决下一个难题……关系的关系。下面的代码大部分是在回答 但我在我的下一个问题的部分代码段的注释中。我将如何进一步查询顶级关系中的关系?很高兴看到您将如何扩展代码来做到这一点@roamer-1888

最新:

//Return a single project
Parse.Cloud.define('getProjectByUrl', function(request, response) {
    var Projects = Parse.Object.extend("projects"); // with credit to @kRiZ
    var query = new Parse.Query(Projects);
    query.equalTo('projectUrl', request.params.projectUrl);
    query.include("projectStatus"); // *MJ Added the include to add the project Status pointer
    query.find().then(function(projectsResult) {
        var project = projectsResult[0];
        //From here, `project` is hierarchically monkey-patched with the results of further queries.

        //Make tags query, the referees query and the sections query in parallel.
        var tagsPromise = project.relation('tags').query().find();
        var refereesPromise = project.relation('referees').query().find();
        var sectionsPromise = project.relation('sections').query().include("sectionType").find(); //*MJ Added the include of the sectionType pointer

        // Aggregate the three promises with Parse.Promise.when(), and handle the responses.
        return Parse.Promise.when(tagsPromise, refereesPromise, sectionsPromise).then(function(tags, referees, sections) {
            project.set('tags', tags);
            project.set('referees', referees);
            project.set('sections', sections);

            //Go deeper into `sections`
            var sectionsRelationsPromises = sections.map(function(section) {
                // *MJ Remove sectionTypesPromise as it's a pointer
                var filesPromise = section.relation('files').query().include("fileType").find(); // *MJ Added the include to grab the fileType pointer
                return Parse.Promise.when(filesPromise).then(function(files) {
                    //*MJ Removed the promise for section Types
                    section.set('files', files);
                    // *MJ Removed the Deeper Logic
                });
            });
            return Parse.Promise.when(sectionsRelationsPromises);
        }).then(function() {
            return project;
        });
    }).then(function(project) {
        // At this point, all the data is gathered in the form of Parse objects in project,
        // which now needs to be mapped into a js plain object.
        var projectData = projectObj(project);
        projectData.tags = project.get('tags').map(tagObj); //Process the tags response
        projectData.referees = project.get('referees').map(refereeObj); // *MJ removed one e from refereeObj //Process the referees response
        projectData.sections = project.get('sections').map(sectionObj); //Process the sections response
        // *MJ Removed the adding of the files and looking over the sections.

        //Yay! (hopfully)
        response.success(projectData);
    }).fail(function(error) {
        response.error('Error: ' + error);
    });

    // ***********************************
    // ***** start: mapper functions *****
    // ***********************************
    function projectObj(project) {
        return { // *MJ Removed the stray equals sign here
            'id': project.id,
            'title': project.get('title'),
            'previewImage': project.get('previewImage'),
            'longDescription': project.get('longDescription'),
            'shortDescription': project.get('shortDescription'),
            'visibleToPublic': project.get('visibleToPublic'),
            'dateStart': project.get('dateStart'),
            'dateEnd': project.get('dateEnd'),
            'updatedAt': project.get('updatedAt'),
            "projectStatus": project.get("projectStatus").get("status") //*MJ Added the get of the Project Status status.
        }
    }
    function tagObj(tag) {
        return {
            'tag': tag.get('tag')
        };
    }
    function refereeObj(referee) {
        return {
            'name': referee.get('name'),
            'role': referee.get('role'),
            'emailAddress': referee.get('emailAddress'),
            'phoneNumber': referee.get('phoneNumber'),
            'linkedInUrl': referee.get('linkedInUrl')
        };
    }
    function sectionObj(section) {
        return {
            'type': section.get('sectionType').get("type"), // *MJ Added the pointer for SectionType > type
            'order': section.get('order'),
            'content': section.get('content'),
            'files': section.get('files').map(fileObj)
        };
    }
    function fileObj(file) {
        return {
            'name': file.get('name'), // *MJ chnaged the name to be more appropriate
            'url': file.get('url'), // *MJ Added the missing comma
            'type': file.get('fileType').get("type") //*MJ Added the pointer for fileType > type and removed semi colon
        };
    }
    // *********************************
    // ***** fin: mapper functions *****
    // *********************************
});

旧:

//Return a single project
Parse.Cloud.define('getProject', function(request, response) {
    var Projects = Parse.Object.extend("projects"); // with credit to @kRiZ
    var query = new Parse.Query(Projects);
    query.equalTo('projectUrl', request.params.projectUrl);
    query.find().then(function(projectsResult) {
        var project = projectsResult[0];
        var projectData = {
            'id': project.id,
            'title': project.get('title'),
            'previewImage': project.get('previewImage'),
            'longDescription': project.get('longDescription'),
            'shortDescription': project.get('shortDescription'),
            'visibleToPublic': project.get('visibleToPublic'),
            'dateStart': project.get('dateStart'),
            'dateEnd': project.get('dateEnd'),
            'updatedAt': project.get('updatedAt')
        };

        //Now make the tags query and the referees query in parallel.
        var tagsPromise = project.relation('tags').query().find();
        var refereesPromise = project.relation('referees').query().find();
        var sectionsPromise = project.relation('sections').query().find();
        var sectionTypesPromise = project.relation('sections').query().find().relation('type').query().find();
        var filesPromise = project.relation('sections').query().find().relation('files').query().find();
        var fileTypesPromise = project.relation('sections').query().find().relation('files').query().find().relation('type').query().find();


        // Aggregate the two promises with Parse.Promise.when(), and handle the responses.
        return Parse.Promise.when(tagsPromise, refereesPromise, sectionsPromise, sectionTypesPromise, filesPromise, fileTypesPromise).then(function(tags, referees, sections, sectionTypes, files, fileTypes) {
            //Process the tags response
            projectData.tags = tags.map(function(tag) {
                return {
                    'tag': tag.get('tag')
                };
            });
            //Process the referees response
            projectData.referees = referees.map(function(refereee) {
                return {
                    'name': refereee.get('name'),
                    'role': refereee.get('role'),
                    'emailAddress': refereee.get('emailAddress'),
                    'phoneNumber': refereee.get('phoneNumber'),
                    'linkedInUrl': refereee.get('linkedInUrl')
                };
            });

            //Process the sections response
            projectData.sections = sections.map(function(section) {
                return {
                    'order': section.get('order'),
                    'content': section.get('content')
                };
            });

            // Problem: Sections have a relations column (files)
            // which I would like to return as a child of sections.
            // The files class then has a pointer column (type)
            // to another class which contains the a list of
            // file types (i.e. Image, Document, etc...)
            // The sections structure of projectDate should
            // look like:
            //
            // "sections": [{
            //   "type": "Section Type"
            //   "order": "1",
            //   "content": "This is the Section content",
            //   "files": [{
            //     "filename": "Image 1",
            //     "url": "image-1.png"
            //     "type": "Image"
            //   },
            //   {
            //     "filename": "Image 2",
            //     "url": "image-2.png",
            //     "type": "Image"
            //   },
            //   {
            //     ...
            //   }]
            //  },
            //  {
            //    ...
            //  }
            // }]

            //Process the section type response. This is reliant on sections being retrieved.
            projectData.sections.type = sections.map(function(sectionTypes) {
                return {
                    'type': sectionTypes.get('type')
                };
            });

            //Process the section files response. This is reliant on sections being retrieved.
            projectData.sections.files = sections.map(function(files) {
                return {
                    'filename': files.get('filename'),
                    'url': files.get('url')
                };
            });

            //Process the section files types response. This is reliant on files being retrieved.
            projectData.sections.files.type = sections.map(function(fileTypes) {
                return {
                    'type': fileTypes.get('type')
                };
            });
            // Currently not so Yay!

            response.success(projectData);
        });
    }).fail(function(error) {
        response.error('Error: ' + error);
    });
});

笼统地对待这个问题:假设您有一个名为 "ClassA" 的 class,它有一个名为 "classBs" 的关系,它与 "ClassB" 的许多实例相关联。并且还说 "ClassB" 个实例有一个称为 "classCs" 的关系,将它们与 "ClassC".

的实例相关联
ClassA --relates to many --< ClassB --relates to many --< ClassC
           ("classBs")                 ("classCs") 

现在,给定 "ClassA" 的单个实例,如何通过 "ClassB" 获取与其相关的所有 "ClassC" 个实例?

答案很简单,记住几件事:(1) 像这里所做的那样非常清楚地阐明数据模型,(2) 用更小、更简单的 promise 返回原语组成更复杂的逻辑 (3)使用 Parse.Promise.or 执行多个查询的联合。

var _ = require("underscore");

// return a promise for many instances of ClassC related to the given aObject
function getCsFromA(aObject) {
    var bRelation = aObject.get("classBs");
    return bRelation.query().find().then(function(bObjects) {
        // gather all of the bObject's relation's queries
        var  queries = _.map(bObjects, function(bObject) {
            return aObject.get("classCs").query();
        });
        // get the union of many queries
        return Parse.Query.or(queries);
    });
}

几个实用点:查询默认限制为 100,您可以将限制更改为最多 1000。最多,一千个关系中的一千个关系是一百万个结果。这肯定会违反 parse.com.

的一些资源限制

深入一层稍微复杂一些。每个级别都需要一个与顶级模式非常相似的模式。

不幸的是,这些模式并不自然地适合 "flat"。不断回顾早期结果的需要使嵌套很有吸引力,尽管可能不是绝对必要的;我确信存在其他方法。

这是对代码的尝试。没法测试,很可能会出错。

//Return a single project
Parse.Cloud.define('getProject', function(request, response) {
    var Projects = Parse.Object.extend("projects"); // with credit to @kRiZ
    var query = new Parse.Query(Projects);
    query.equalTo('projectUrl', request.params.projectUrl);
    query.find().then(function(projectsResult) {
        var project = projectsResult[0];
        //From here, `project` is hierarchically monkey-patched with the results of further queries.

        //Make tags query, the referees query and the sections query in parallel.
        var tagsPromise = project.relation('tags').query().find();
        var refereesPromise = project.relation('referees').query().find();
        var sectionsPromise = project.relation('sections').query().find();

        // Aggregate the three promises with Parse.Promise.when(), and handle the responses.
        return Parse.Promise.when(tagsPromise, refereesPromise, sectionsPromise).then(function(tags, referees, sections) {
            project.set('tags', tags);
            project.set('referees', referees);
            project.set('sections', sections);

            //Go deeper into `sections`
            var sectionsRelationsPromises = sections.map(function(section) {
                var sectionTypesPromise = section.relation('type').query().find();
                var filesPromise = section.relation('files').query().find();
                return Parse.Promise.when(sectionTypesPromise, filesPromise).then(function(sectionTypes, files) {
                    section.set('type', sectionTypes[0]);
                    section.set('files', files);
                    //And deeper still into each of the section's files to find their types
                    var filesRelationsPromises = files.map(function(file) {
                        return file.relation('type').query().find().then(function(fileTypes) {
                            file.set('type', fileTypes[0]);
                        });
                    });
                    return Parse.Promise.when(filesRelationsPromises);
                });
            });
            return Parse.Promise.when(sectionsRelationsPromises);
        }).then(function() {
            return project;
        });
    }).then(function(project) {
        // At this point, all the data is gathered in the form of Parse objects in project,
        // which now needs to be mapped into a js plain object.
        var projectData = projectObj(project);
        projectData.tags = project.get('tags').map(tagObj); //Process the tags response
        projectData.referees = project.get('referees').map(refereeeObj); //Process the referees response
        projectData.sections = project.get('sections', sections).map(sectionObj); //Process the sections response
        projectData.sections.each(function(section) {
            section.files = section.get('files').map(fileObj);
        });
        //Yay! (hopfully)
        response.success(projectData);
    }).fail(function(error) {
        response.error('Error: ' + error);
    });

    // ***********************************
    // ***** start: mapper functions *****
    // ***********************************
    function projectObj(project) {
        return = {
            'id': project.id,
            'title': project.get('title'),
            'previewImage': project.get('previewImage'),
            'longDescription': project.get('longDescription'),
            'shortDescription': project.get('shortDescription'),
            'visibleToPublic': project.get('visibleToPublic'),
            'dateStart': project.get('dateStart'),
            'dateEnd': project.get('dateEnd'),
            'updatedAt': project.get('updatedAt')
        }
    }
    function tagObj(tag) {
        return {
            'tag': tag.get('tag')
        };
    }
    function refereeObj(referee) {
        return {
            'name': referee.get('name'),
            'role': referee.get('role'),
            'emailAddress': referee.get('emailAddress'),
            'phoneNumber': referee.get('phoneNumber'),
            'linkedInUrl': referee.get('linkedInUrl')
        };
    }
    function sectionObj(section) {
        return {
            'type': section.get('type'),
            'order': section.get('order'),
            'content': section.get('content'),
            'files': section.get('files').map(fileObj)
        };
    }
    function fileObj(file) {
        return {
            'filename': file.get('filename'),
            'url': file.get('url')
            'type': file.get('type');
        };
    }
    // *********************************
    // ***** fin: mapper functions *****
    // *********************************
});

我已经使代码尽可能简单:

  • 将第一个 .then 的回调限制为异步收集数据。
  • 在后续的 .then 回调中编排所收集数据的映射。
  • 将各个映射器函数提取到末尾的单独部分中。

相信我,这比在一个块中完成所有操作更具可读性。我试过了,真是噩梦。

调试愉快。