centralize mongo schema handling logic

Author: drew-gross

src/Adapters/Storage/Mongo/MongoSchemaCollection.js

@@ -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;
 }
 

src/Adapters/Storage/Mongo/MongoStorageAdapter.js

@@ -37,6 +37,15 @@ const storageAdapterAllCollections = mongoAdapter => {
 const convertParseSchemaToMongoSchema = ({...schema}) => {
   delete schema.fields._rperm;
   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;
 }