forked from parse-community/parse-server
-
Notifications
You must be signed in to change notification settings - Fork 16
Updating the latest version #2
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
Merged
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
* Move helper.clearData to DatabaseAdapter. Expose DatabaseAdapter in index * fix indentation * Export DatabaseAdapter in index.js * Rename clearData to destroyAllDataPermanently. Only export destroyAllDataPermanently from DatabaseAdapter. Update helper * Expose wrapped TestUtils from index.js. TestUtils exposed select functions from other modules, only in test environment
…uery (#1450) * Removing sessionToken and authData from _User objects included in a query This bug caused sessionToken to be replaced on client side to some old sessionToken from DB. * Removing dangling variable that is never used
* Schema.js database agnostic * nits
* Remove collection prefix from DB Controller * Remove collection prefix from cache * Revert "Remove collection prefix from cache" This reverts commit 529d67d. * Remove knowledge of default mongo URI from Parse Server * Remove adaptive collection paramater from deleteFields * Tidy up DBAdapter.js
* Removing sessionToken and authData from _User objects included in a query This bug caused sessionToken to be replaced on client side to some old sessionToken from DB. * Removing dangling variable that is never used * Checking if object has defined key for Pointer constraints in liveQuery If there is a liveQuery subscription, with Pointer type constrains (e.g query.equalTo('user', Parse.User.current())), and new object has undefined value for that field, we get this error: error: Uncaught internal server error. [TypeError: Cannot read property 'className' of undefined] TypeError: Cannot read property 'className' of undefined at matchesKeyConstraints (…/node_modules/parse-server/lib/LiveQuery/QueryTools.js:145:51)
* Moves transform to MongoTransform - Adds ACL query injection in MongoTransform * Removes adaptiveCollection from DatabaseController - All collections manipulations are now handled by a DBController - Adds optional flags to configure an unsafe databaseController for direct access - Adds ability to configure RestWrite with multiple writes - Moves some transfirmations to MongoTransform as they output specific code * Renames Unsafe to WithoutValidation
* Remove results if limit = 0; * Adds tests for limit=0 and count=1. * Improves readability.
Changelog and update to 2.2.7
* Tidy up schemas router * de-duplicate logic for injecting default schemas * Remove no-op promise * use hasClass * Make getAllSchemas part of SchemaController * Move getOneSchema logic onto schema controller * remove log
* Move "No two geopoints" logic into mongo adapter * Semicolon
* Rename Schema to SchemaController * Rename Schema => SchemaController * Move to controllers folder * Move SchemasController to Controllers folder * remove ./..
Fixes error thrown by #1526
* Tidy up transformKeyValue * Specialize transformKeyValue for object creation * remove keys that never appear in creation requests * rename function * remove local var * early exit for simple keys * Refactor create * Force class creation when creating an object * Pass parameters to key value transformer * No need to check for array in this func * start using Parse Format schema in MongoTransform * Remove call to getExpectedType * add tests to ensure client can't see _PushStatus
This test depends on external services and is super flaky. Lets kill it.
* WIP: Initial pointer permissions * Process Pointer perms when no matching CLP are found * Additional tests with read lockdown * Create operation lockdown with pointer permissions, on parse.com, when an class is locked down with write pointer perm, users can't create objects even if they set their own as the pointer permission key * Adds test case for multiple write PointerPerms * Adds validation for pointer permissions when setting * Adds tests for validating pointer permissions column types * Adds tests for complex ACL/CLP/PP hierarchy * Restores power of the master * Adds validation of borked fields * Adds complex test for find * Adds more variations around PointerPermissions tests
This allows access to logging inside cloud code and triggers via request.log.info request.log.error
* removes mongo style props from _PushStatus * removes log * Update MongoTransform.js Removes _id case
* destructuring in DB controller * deleteObject in db adapter * Turns out we can't have delete by object ID because of ACLs... * Fix tests * destructure acl * Don't reject with object
* Move writeACL knowledge out of mongoAdapter * Remove write ACL from mongo adapter * Remove readACL from Mongo Transform
* Some cleanup for deleting one schema * tidyness * Remove _allCollections as Parse Server doesn't need it.
* Test case to ensure dashboard.parse.com won't break * Adds volatile classes concept for _PushStatus * Fixes test
davimacedo
pushed a commit
that referenced
this pull request
Apr 17, 2019
davimacedo
pushed a commit
that referenced
this pull request
Jul 22, 2019
Graphql config merge master
davimacedo
pushed a commit
that referenced
this pull request
Jul 17, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.