The problem this pr is trying to solve:
When an error occurs on the server, a message should
be returned to the client, and a message should be logged.
Currently, on the server, the log is just [object, object]
This pr will stop calling the default express error handler
which causes two problems: 1. it writes to console instead of log file
2. the output is completely useless! :)
Instead, we'll log the error ourselves using the ParseServer's logger.
fixes: #661
Get GCSAdapter up to snuff with FilesController + FilesControllerTestFactory
* 'master' of https://github.com/ParsePlatform/parse-server: (102 commits)
Remove duplicated instructions
Release and Changelog for 2.1.4
fixes missing coverage with sh script
Fix update system schema
Adds optional COVERAGE
Allows to pass no where in $select clause
Sanitize objectId in
Fix delete schema when actual collection does not exist
Fix replace query overwrite the existing query object.
Fix create system class with relation/pointer
Use throws syntax for errors in SchemasRouter.
Completely migrate SchemasRouter to new MongoCollection API.
Add tests that verify installationId in Cloud Code triggers.
Propagate installationId in all Cloud Code triggers.
Add test
expiresAt should be a Date, not a string. Fixes#776
Fix missing 'let/var' in OneSignalPushAdapter.spec.
Don't run any afterSave hooks if none are registered.
Fix : remove query count limit
Flatten custom operations in request.object in afterSave hooks.
...
