Skip to content

Conversation

yuki-takeichi
Copy link
Contributor

@yuki-takeichi yuki-takeichi commented Nov 19, 2016

This PR fixes a compatibility issue for saving Relation object.

Request:

curl -X POST \
  -H 'X-Parse-Application-Id: XXX' \
  -H 'X-Parse-Master-Key:  YYY' \
  -H 'Content-Type: application/json' \
  -d '{"aRelation":{"__type":"Relation","className":"Foo"}}' \
https://api.parse.com/1/classes/Foo

Response from api.parse.com:

{"createdAt":"2016-11-19T11:53:04.087Z","objectId":"blEqHPUBuk"}

(Parse Class Foo and its field aRelation are created implicitly.)

Response from parse-server:

{"code":111,"error":"This is not a valid Relation"}

@flovilmart flovilmart merged commit 4ea455b into parse-community:master Nov 20, 2016
rsouzas pushed a commit to back4app/parse-server that referenced this pull request Dec 3, 2016
* support Parse.Relation object save

* prevent Relation object from being saved in storage
rsouzas pushed a commit to back4app/parse-server that referenced this pull request Dec 3, 2016
Jcarlosjunior pushed a commit to back4app/parse-server that referenced this pull request Dec 13, 2016
* support Parse.Relation object save

* prevent Relation object from being saved in storage
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants