joe/kami-parse-server
Public Access
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

centralize mongo schema handling logic

Browse Source
This commit is contained in:
Drew Gross
2016-06-13 13:14:29 -07:00
parent a69a88f3a4
commit 510a890a03
2 changed files with 9 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/Adapters/Storage/Mongo/MongoSchemaCollection.js
View File

@@ -126,12 +126,6 @@ function mongoSchemaFromFieldsAndClassNameAndCLP(fields, className, classLevelPe
} }
} }
// Legacy mongo adapter knows about the difference between password and _hashed_password.
// Future database adapters will only know about _hashed_password.
// Note: Parse Server will bring back password with injectDefaultSchema, so we don't need
// to add it here.
delete mongoObject._hashed_password;
return mongoObject; return mongoObject;
} }

9
src/Adapters/Storage/Mongo/MongoStorageAdapter.js
View File

@@ -37,6 +37,15 @@ const storageAdapterAllCollections = mongoAdapter => {
const convertParseSchemaToMongoSchema = ({...schema}) => { const convertParseSchemaToMongoSchema = ({...schema}) => {
delete schema.fields._rperm; delete schema.fields._rperm;
delete schema.fields._wperm; delete schema.fields._wperm;
if (schema.className === '_User') {
// Legacy mongo adapter knows about the difference between password and _hashed_password.
// Future database adapters will only know about _hashed_password.
// Note: Parse Server will bring back password with injectDefaultSchema, so we don't need
// to add _hashed_password back ever.
delete schema.fields._hashed_password;
}
return schema; return schema;
} }