updated master #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* fix(package): update mongodb to version 3.4.1 * chore(package): update lockfile package-lock.json
* chore(package): update eslint to version 6.8.0 * chore(package): update lockfile package-lock.json
* 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
* chore(package): update nyc to version 15.0.0 * chore(package): update lockfile package-lock.json
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
* fix(package): update parse to version 2.11.0 * chore(package): update lockfile package-lock.json
* fix(package): update pg-promise to version 10.3.2 * chore(package): update lockfile package-lock.json
* fix(package): update apollo-server-express to version 2.9.15 * chore(package): update lockfile package-lock.json
* 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
* chore(package): update flow-bin to version 0.115.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 <[email protected]>
stevestencil
pushed a commit
that referenced
this pull request
Aug 25, 2020
* Before Connect + Before Subscribe #1 * Cleanup and Documentation * Add E2E tests * Bump parse to 2.15.0 Co-authored-by: Diamond Lewis <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.