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

Adds more expressive schema mismatch errors (#2662)

Browse Source
This commit is contained in:
Florent Vilmart
2016-09-09 14:41:11 -04:00
committed by GitHub
parent 364604e181
commit fc576cb415
2 changed files with 66 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
src/Controllers/SchemaController.js
View File

@@ -299,6 +299,13 @@ const dbTypeMatchesObjectType = (dbType, objectType) => {
return false;
}
const typeToString = (type) => {
if (type.targetClass) {
return `${type.type}<${type.targetClass}>`;
}
return `${type.type || type}`;
}
// Stores the entire schema of the app in a weird hybrid format somewhere between
// the mongo format and the Parse format. Soon, this will all be Parse format.
export default class SchemaController {
@@ -592,7 +599,7 @@ export default class SchemaController {
if (!dbTypeMatchesObjectType(expectedType, type)) {
throw new Parse.Error(
Parse.Error.INCORRECT_TYPE,
`schema mismatch for ${className}.${fieldName}; expected ${expectedType.type || expectedType} but got ${type.type}`
`schema mismatch for ${className}.${fieldName}; expected ${typeToString(expectedType)} but got ${typeToString(type)}`
);
}
return this;