* fix(package): update graphql to version 14.6.0
* chore(package): update lockfile package-lock.json
Co-authored-by: Antonio Davi Macedo Coelho de Castro <adavimacedo@gmail.com>
* chore(package): update @babel/cli to version 7.8.3
* chore(package): update @babel/plugin-proposal-object-rest-spread to version 7.8.3
* chore(package): update @babel/plugin-transform-flow-strip-types to version 7.8.3
* chore(package): update @babel/preset-env to version 7.8.2
* chore(package): update lockfile package-lock.json
* Relax regex for customId ; allow varying id length
* test
* remove trycatch, fix typo
* de-duplicate test names; test pointer targetclass
* fixed early return; detailed errors for protected
* added hint to aggregate
* added support for hint in query
* added else clause to aggregate
* fixed tests
* updated tests
* Add tests and clean up
* Add support for explain
Co-authored-by: Diamond Lewis <findlewis@gmail.com>
* chore(package): update @babel/cli to version 7.8.0
* chore(package): update @babel/core to version 7.8.0
* chore(package): update @babel/plugin-proposal-object-rest-spread to version 7.8.0
* chore(package): update @babel/plugin-transform-flow-strip-types to version 7.8.0
* chore(package): update @babel/preset-env to version 7.8.0
* chore(package): update lockfile package-lock.json
* fix(GraphQL): Unable to run queries with order as array
An internal server error is thrown if the `order` query parameter is an array.
Currently, `order` only works with a single value.
* Add tests
* Reset cache
* Remove one of the tests from Postgres
Co-authored-by: Douglas Muraoka <douglas.muraoka@gmail.com>
* fix(GraphQL): Timeout when fetching huge collections
Currently, when not specifying a `limit` to the GraphQL find-like query, it tries to fetch the entire collection of objects from a class. However, if the class contains a huge set of objects, it is never resolved and results in timeout.
In order to solve this kind of problem, `parse-server` allows us to define a `maxLimit` parameter when initialized, which limits the maximum number of objects fetched per query; but it is not properly considered when the `limit` is undefined.
* fix: Keep same behavior as REST fetch
https://community.parseplatform.org/t/server-log-retention/867/2
Maximum number of logs to keep. If not set, no logs will be removed. This can be a number of files or number of days. If using days, add 'd' as the suffix. (default: null).
I'll run this in production for a few days. I assume it works.
Useful for saving disk space.
Update winston-daily-rotate-file package to 4.4.0
* chore(package): update @babel/cli to version 7.7.7
* chore(package): update @babel/core to version 7.7.7
* chore(package): update @babel/plugin-proposal-object-rest-spread to version 7.7.7
* chore(package): update @babel/preset-env to version 7.7.7
* chore(package): update lockfile package-lock.json
* Update PostgresStorageAdapter.js
Improving use of the `await.async` notation in relation to `pg-promise`, and in general.
* Update PostgresStorageAdapter.js
* Update PostgresStorageAdapter.js
Correcting some results.
* Update PostgresStorageAdapter.js
* chore(package): update apollo-cache-inmemory to version 1.6.5
* chore(package): update apollo-client to version 2.6.6
* chore(package): update apollo-utilities to version 1.3.3
* chore(package): update lockfile package-lock.json