beforeSave issues with dirtyKeys about parse-sdk-js

[stanleyw]

Currently this is not supported by webhooks. The dirty keys are not passed to webhooks by the Parse backend according to the current spec (https://www.parse.com/docs/js/guide#cloud-code-advanced-beforesave-webhooks), so the JS SDK can't populate this field in Node.js.

However, we are always looking to improve the platform. Could you talk more about your use case and why you need this information?

[Silkjaer]

Thanks for the reference, I was looking all over for this.

I am relying on some node.js plugins that I can't implement in CloudCode, so I made a quick decision to move all code to Heroku (without noticing the dirtyKeys limitation). I want to avoid maintaining server side logic in too many places :)

I am often using the change of a key's value as a trigger to another action, e.g. updating a related object. I do not want to trigger these actions on every save, but only if a specific key's value is changed.

I am also validating keys if they are dirty, e.g. to set a default value or verify it is not undefined.

Would it be possible to somehow trigger a warning log message if unsupported functions are used?

Thanks!

On 30. sep. 2015, at 19.11, Stanley Wang [email protected] wrote:

Currently this is not supported by webhooks. The dirty keys are not passed to webhooks by the Parse backend according to the current spec (https://www.parse.com/docs/js/guide#cloud-code-advanced-beforesave-webhooks), so the JS SDK can't populate this field in Node.js.

However, we are always looking to improve the platform. Could you talk more about your use case and why you need this information?

—
Reply to this email directly or view it on GitHub.

[andrewimm]

@Zicker are you referring to code running in Node.js, or on Parse Cloud Code?
This issue is regarding code running on a privately hosted Node server, using our Webhooks service.

That said, the behavior you mention should still be supported in 1.6. We have tests that suggest it works in the current version (1.6.4)

[stanleyw]

@Silkjaer please see https://github.com/ParsePlatform/parse-cloud-express/issues/4