Create object behaviour change from 2.2.17 to 2.2.18

[btanev]

Please read the following instructions carefully.

Check out #1271 for an ideal bug report.
The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!

Many members of the community use Stack Overflow and Server Fault to ask questions.
Read through the existing questions or ask your own!

• Stack Overflow: http://stackoverflow.com/questions/tagged/parse.com
• Server Fault: https://serverfault.com/tags/parse

For database migration help, please file a bug report at https://parse.com/help#report

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

• You've met the prerequisites: https://github.com/ParsePlatform/parse-server/wiki/Parse-Server-Guide#prerequisites.
• You're running the latest version of Parse Server: https://github.com/ParsePlatform/parse-server/releases
• You've searched through existing issues: https://github.com/ParsePlatform/Parse-Server/issues?utf8=%E2%9C%93&q=is%3Aissue Chances are that your issue has been reported or resolved before.
• You have filled out every section below. Issues without sufficient information are more likely to be closed.

Issue Description

After updating to parse-server 2.2.18 I've notice a behaviour change when creating an Object using the REST API. In the 2.2.18 the response is missing the additional object fields and contains only the common fields like objectId, createdAt, ACL

Steps to reproduce

Common setup

We have one class defined in the schema e.g. Author that have only one field displayName.

Using parse-server 2.2.17

1. Request

POST https://<serverUrl>/parse/classes/Author
X-Parse-Application-Id:<applicationId>
X-Parse-Master-Key:<masterKey>

{"displayName": "a test 2.2.17"}

1. Response

HTTP/1.1 201 Created
X-Powered-By: Express
Location: https://<serverUrl>/parse/classes/Author/HAy5pEcw5c
ETag: W/"c7-8imG5HhXN6+NNJ9Fq9R14Q"

{
    "objectId": "HAy5pEcw5c",
    "createdAt": "2016-08-23T10:37:15.062Z",
    "ACL": {
        "*": {
            "read": true
        },
        "role:Admin": {
            "read": true,
            "write": true
        }
    },
    "displayName": "a test 2.2.17",
    "updatedAt": "2016-08-23T10:37:15.062Z"
}

Using parse-server 2.2.18

1. Request

POST https://<serverUrl>/parse/classes/Author
X-Parse-Application-Id:<applicationId>
X-Parse-Master-Key:<masterKey>

{"displayName": "a test 2.2.18"}

1. Response

HTTP/1.1 201 Created
X-Powered-By: Express
Location: https://<serverUrl>/parse/classes/Author/w3xGbKIF4O
ETag: W/"82-/MIA4WGnKv9M4f9+zrku7A"

{
    "objectId": "w3xGbKIF4O",
    "createdAt": "2016-08-23T10:51:02.525Z",
    "ACL": {
        "*": {
            "read": true
        },
        "role:Admin": {
            "read": true,
            "write": true
        }
    }
}

As you can see the fields displayName and updatedAt are missing from the response.

Question

Is this an expected behaviour? I haven't read about this change in the changelog from 2.2.17 to 2.2.18

We've found this problem after upgrading to 2.2.18 and executing our integration tests.

[mmazzarolo]

Having the same issue on 2.2.18 (2.2.17 works correctly).

[joeyslack]

Indeed. Having to use 2.2.17 currently.

[flovilmart]

That's odd indeed. it wasn't supposed to be affected.

[flovilmart]

I'll have a looks tonight and try to provide a patch ASAP

[flovilmart]

Issue originates from: e4c2e65#diff-3646535e0655c134862bb00401c8097cR942

Fix don't seem trivial

[flovilmart]

@btanev alright, went back a bit, checking here: http://parseplatform.github.io/docs/rest/guide/#creating-objects the REST call should only return createdAt and objectId, as well as keys that have been set by Cloud Code hooks.

The behaviour < 2.2.18 was 'broken'.

[btanev]

Hi @flovilmart

If it is by spec then it is by spec. Thanks for checking this out.

Do you guys have in your backlog items that are going to change this behaviour?

Can I suggest a change in the behaviour of POST and PUT requests? If they are returning the "changed" fields this will reduce the requests to the server. Right now in 2.2.18+ we have to do a POST / PUT and then to make sure we have the correct Object state we have to do a follow up GET request.

[flovilmart]

@btanev We should not change that behaviour in the future, there still maybe some quirks that don't match with the original documentation, so when in doubt, I ever go back to the original documentation.

As it's stated, it should only return changed fields as well as createdAt and objectId on POST, updatedAt on PUT.

If it isn't we should make sure that it the case, I believe there is a test that covers it (https://github.com/ParsePlatform/parse-server/blob/master/spec/ParseAPI.spec.js#L819)

[flovilmart]

@btanev, i'm closing that one as the behavior is what's expected from the documentation