fix(direct-access): save context not present if direct access enabled (…

…#6764)

* fix(direct-access): save context not present if direct access enabled

[Open discussion](#6459) for feature with other issues

* only send context when present

* use object spread

* revert and add test

* rename test

Co-authored-by: dplewis <findlewis@gmail.com>

spec/ParseServerRESTController.spec.js

@@ -161,9 +161,9 @@ describe('ParseServerRESTController', () => {
                 expect(databaseAdapter.createObject.calls.argsFor(0)[3]).toBe(
                   databaseAdapter.createObject.calls.argsFor(1)[3]
                 );
-                expect(results.map(result => result.get('key')).sort()).toEqual(
-                  ['value1', 'value2']
-                );
+                expect(
+                  results.map(result => result.get('key')).sort()
+                ).toEqual(['value1', 'value2']);
                 done();
               });
             });
@@ -517,6 +517,22 @@ describe('ParseServerRESTController', () => {
       });
   });
 
+  it('should handle a POST request with context', async () => {
+    Parse.Cloud.beforeSave('MyObject', req => {
+      expect(req.context.a).toEqual('a');
+    });
+    Parse.Cloud.afterSave('MyObject', req => {
+      expect(req.context.a).toEqual('a');
+    });
+
+    await RESTController.request(
+      'POST',
+      '/classes/MyObject',
+      { key: 'value' },
+      { context: { a: 'a' } }
+    );
+  });
+
   it('ensures sessionTokens are properly handled', done => {
     let userId;
     Parse.User.signUp('user', 'pass')