-
-
Notifications
You must be signed in to change notification settings - Fork 596
Unsaved children are not able to be saved when updating parent object #89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This was referenced Nov 10, 2015
fkling
added a commit
to fkling/astexplorer
that referenced
this issue
Dec 10, 2015
Switching to ES6 class declarations requires to "register" the subclass with Parse, according to the documentation: https://parse.com/docs/js/guide#objects-parse-object. There seems to be a bug (feature?) in Parse v1.6 where it isn't possible anymore to add a new object to an existing collection and just save the parent object: parse-community/Parse-SDK-JS#89.
Resolved in 5e86f78, will be released in 1.6.14 |
ionisaligox72
added a commit
to ionisaligox72/astexplorer
that referenced
this issue
Aug 7, 2024
Switching to ES6 class declarations requires to "register" the subclass with Parse, according to the documentation: https://parse.com/docs/js/guide#objects-parse-object. There seems to be a bug (feature?) in Parse v1.6 where it isn't possible anymore to add a new object to an existing collection and just save the parent object: parse-community/Parse-SDK-JS#89.
my2
added a commit
to my2/astexplorer
that referenced
this issue
Aug 13, 2024
Switching to ES6 class declarations requires to "register" the subclass with Parse, according to the documentation: https://parse.com/docs/js/guide#objects-parse-object. There seems to be a bug (feature?) in Parse v1.6 where it isn't possible anymore to add a new object to an existing collection and just save the parent object: parse-community/Parse-SDK-JS#89.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Adding to our list of items in #73.
In the below code we make two classes
Brand
andItem
. Let's say that Brands can have many Items and that this relationship is modeled by an array ofItem
pointers set on the "items" field forBrand
.We then create a new
Item
andBrand
, setting theitem
as an array of pointer onbrand
.It saves just fine. Parse realized that
item
is unsaved and persists it before savingbrand
. It follows up by savingbrand
and resolving the promise.However, if we then try to add unsaved objects to the already persisted brand it becomes unable to save the unsaved objects giving the error:
Setup
Test
This seems like a bug. It works just fine in the 1.5 SDK. Please let me know what you think. Also I'd love to help fix it if you point me in the right direction. Anything I can do to help, let me know.
The text was updated successfully, but these errors were encountered: