-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
add invalid __type check #674
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
Conversation
@sdf611097 updated the pull request. |
} | ||
break; | ||
case 'File' : | ||
if(obj.url && obj.name) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
name
is actually the only required field on a file. In most cases, the url can & should be constructed during read. We were actually discussing making url required earlier today, but decided against it for now.
@sdf611097 updated the pull request. |
|
I think I miss something, so that my test failed. here is the output of npm test npm test
◝ Starting a MongoDB deployment to test against...
Started TypeError: Cannot read property 'latitude' of undefined |
@sdf611097 updated the pull request. |
@sdf611097 updated the pull request. |
I'm sorry for test failed again and again, but I have no idea why failed in ParseGeoPoint.spec.js:93:7. coverage not measured fully. <= Does this cause by non up-to-date base? |
Is there any usage to use __type in obj?
Do I add further check, such as __type=="File" must contains url, name?