Skip to content
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

Adding a test demonstrating issue #1942. #1943

Conversation

airdrummingfool
Copy link
Contributor

This test demonstrates #1942: saving an object after calling set('key', undefined) does not result in key being undefined in object's beforeSave. I originally thought this was Cloud Code only, but that is not the case.

@flovilmart
Copy link
Contributor

This one seems to be a JS-SDK behaviour. When you do set('key', undefined), the JS-SDK registers it as a no-op as this is equivalent/equal to calling set('key')

@flovilmart flovilmart closed this May 29, 2016
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.

2 participants