update function and freeze schema

[lucianmat]

added user, isMaster, installationId on functions as Parse.Cloud.FunctionRequest specs .

changed route path to '/functions/:functionName+', that way function can be requested with extra path components as : Parse.Cloud.run('workflows/list', {})

[lucianmat]

As discused in #90 :)

[lucianmat]

@natanrolnik If you use Parse JS Sdk, you will get installationId by default, on every request, as it is sent on body payload :

_ApplicationId: "myAppId"
_ClientVersion: "js1.6.14"
_InstallationId: "472605e6-8067-57e1-6c01-c69bd6502d03"
_JavaScriptKey: "unused"

[natanrolnik]

Cool. I'll check regarding the iOS SDK. Maybe @nlutsenko can quickly answer here?

[lucianmat]

have also #39 fix proposed.
Schema creation/update is locked unless NODE_ENV==='development' or master key is used

[nlutsenko]

Installation ID is passed as a header to every single API request sent against a server.
@gfosco, I couldn't find the code for parsing it - do we inflate the installation id from the header or is it only handled as a parameter for _Installation collection?

[gfosco]

Why the + sign here?

[lucianmat]

• will allow to have a structured calls on functions, such as

Parse.Cloud.run('workflow/list', { objs : true}), 

extending functions reach.
It is an optional route parameter from express, it will be ignored if it is not present and it will work as pervious.

[lucianmat]

It requires latest express and path-to-regexp version, otherwise it will fallback to initial behaviour.

[gfosco]

The installation id is parsed from the headers here: https://github.com/ParsePlatform/parse-server/blob/master/middlewares.js#L22

This is a reasonable solution for the client class creation option... I wanted it to be an option passed to ParseServer, but this is easier and makes sense. Anyone have an issue with it?

[andrewoons]

I think it's better to provide an option that you can pass to ParseServer, so you have more control (e.g. sometimes I don't want schema to update in dev env or sometimes I do want it to update on production).

Maybe that should be in a separate PR too?

[lucianmat]

A more complex solution will be needed if/when ParseServer will be multi-application, and this may be an architectural decision. This is the reason why I did preferred to get up-and-running, solution.

@andrewoons : Env variable may be easily changed outside of code, and if you send masterKey you may be able to change everything. May be used a distinct env variable name to configure, but I don't think it will make a real difference.

[natanrolnik]

@lucianmat any specific reason made you close this PR?
I ask because although #90 was closed, it still depends on this PR if I'm correct.

[gfosco]

Yeah I'd still like to see the freeze method here for disabling client-class-creation... I understand if you were just cleaning this up because of all the rebasing.. Also, the req.user issue with functions got updated already in #172.

[natanrolnik]

Awesome!

[lucianmat]

@natanrolnik it needed to rebase the code, as @gfosco had guessed . I'll resubmit PR after cleaning up, and adding some tests and documentation for proposed behaviour.