-
Notifications
You must be signed in to change notification settings - Fork 17
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
[ARRCONN-154] Added shema models and tests #21
base: master
Are you sure you want to change the base?
[ARRCONN-154] Added shema models and tests #21
Conversation
793961d
to
bcbab6d
Compare
816238b
to
5a520f7
Compare
3f84566
to
cd0e828
Compare
The rest was also added! |
9003aa4
to
29f46f7
Compare
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.
The Like model is still failing the unit tests for me:
Like
✓ should create like based on place
Uncaught Exception expected undefined to be an object
AssertionError: expected undefined to be an object
at Assertion.fail (/Users/jvennemann/Development/appc/appc.arrowdb/node_modules/should/lib/assertion.js:228:17)
at Assertion.prop.(anonymous function) [as Object] (/Users/jvennemann/Development/appc/appc.arrowdb/node_modules/should/lib/assertion.js:69:14)
at /Users/jvennemann/Development/appc/appc.arrowdb/test/test-like.js:58:23
Can you please check?
The following test returns the following error:
|
ada4378
to
29f46f7
Compare
# Conflicts: # package.json
I have reverted the commit where the chat unit test were skipped, because I guess it was an issue related to the arrowdb restriction found by you. |
Although the chat model doesn't allow batch operations it could indeed be possible that this was caused by the API rate limiting. I'll do a new FR when #23 is merged. |
https://jira.appcelerator.org/browse/ARRCONN-154