-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Date objects in cloud functions are not same as hosted parse #2214
Comments
Test failure: |
This seems to be related / opposite of #1826 @drew-gross where should we go from here? |
I think we should always be matching Parse.com behaviour, even if that behaviour is weird. |
I'll add it to #2297 |
flovilmart
added a commit
that referenced
this issue
Jul 16, 2016
drew-gross
pushed a commit
that referenced
this issue
Jul 19, 2016
rsouzas
pushed a commit
to back4app/parse-server
that referenced
this issue
Mar 15, 2017
…ons (parse-community#2297) * fix for parse-community#2294 * fail tests * Makes sure dates are compatible with Parse.com CloudCode parse-community#2214 * Adds regression tests for parse-community#2204
rsouzas
pushed a commit
to back4app/parse-server
that referenced
this issue
Mar 16, 2017
…ons (parse-community#2297) * fix for parse-community#2294 * fail tests * Makes sure dates are compatible with Parse.com CloudCode parse-community#2214 * Adds regression tests for parse-community#2204
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am calling a cloud function with parameters
{date: new Date()}
.This is sent over the wire as:
In the hosted parse function, the date object is untouched
In parse-server the date object gets flattned to just the date string:
Environment Setup
The text was updated successfully, but these errors were encountered: