* Removes need to use babel-register
- Adds watch to watch changes when running the test to regenerate
- Tests are now pure node 8
* Adds timing to helper.js
* Update contribution guide
* Adds inline sourcemaps generation to restore coverage
* nits
* chore(package): update jasmine to version 3.0.0
Closes#4547
* Fixes failing tests for jasmine 3.0
Starting 3.0, done(something) will fail
* Update tests so they dont leverage var, but let and const
With jasmine 3.0, the randomization engine was making the test fails because of the scope of `var`
* Remove randomizer
* Use same adapter for PG tests, drop table to ensure the tests dont side effect
* Adds flow types / Configuration interfaces
* Lets call it options
* Use a single interface to generate the configurations
* Translates options to definitions only if comments are set
* improves logic
* Moves objects around
* Fixes issue affecting logging of circular objects
* fixes undefined env
* Moves all defaults to defaults
* Adds back CLI defaults
* Restored defaults in commander.js
* Merge provided defaults and platform defaults
* Addresses visual nits
* Improves Config.js code
* Adds ability to pass the default value in trailing comments
* Load platform defaults from the definitions file
* proper default values on various options
* Adds ParseServer.start and server.start(options) as quick startup methods
* Moves creating liveQueryServer http into ParseServer.js
* removes dead code
* Adds tests to guarantee we can start a LQ Server from main module
* Fixes incorrect code regading liveQuery init port
* Start a http server for LQ if port is specified
* ensure we dont fail if config.port is not set
* Specify port
* ignore other path skipped in tests
* Adds test for custom middleware setting
* Refactors new Config into Config.get
- Hides AppCache from ParseServer.js, use Config.put which validates
* Extracts controller creation into Controllers/index.js
- This makes the ParseServer init way simpler
* Move serverURL inference into ParseServer
* review nits
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.
...
