-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Closed
Description
Issue Description
The introduction of making the trigger context accessible when saving an object (#6459) did not account for 2 use cases:
- No
contextis set when saving an existing object as discovered by @marcinjakubowski Make trigger context accessible in save #6459 (comment):
const obj = new Parse.Object("TestObject");
await obj.save(null);
await obj.save(null, { context: { a: 'a' } });
- The
contextis not set when cascade-saving objects so thatcontextis inherited by child objects (obj2in this example) as discovered by @davbeck Make trigger context accessible in save #6459 (comment):
const obj = new Parse.Object("TestObject");
const obj2 = new Parse.Object("TestObject2");
obj.set("obj2", obj2);
await obj.save(null, { context: { a: 'a' } });
TODOs:
- Changes in Parse JS SDK fix context when cascade-saving objects Parse-SDK-JS#1186
- Changes in Parse Server fix context for cascade-saving and saving existing object #6735
- no doc changes necessary
Metadata
Metadata
Assignees
Labels
No labels