From fbc4c5e82ef75c6cbf37245c4eec30f4492f9dcc Mon Sep 17 00:00:00 2001 From: Maxime Quandalle Date: Thu, 14 May 2015 12:24:16 +0200 Subject: Disable collection2 transformations in migration functions Fixes #156. --- server/migrations.js | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/server/migrations.js b/server/migrations.js index ce4724cc..2a8e338c 100644 --- a/server/migrations.js +++ b/server/migrations.js @@ -9,9 +9,15 @@ // that would work at the time we write the migration but would break in the // future when we'll update again the concerned collection schema. // -// To prevent this bug we always have to set the `validate` option to false. We -// generally use the shorthandlers defined below. -var noValidate = { validate: false }; +// To prevent this bug we always have to disable the schema validation and +// argument transformations. We generally use the shorthandlers defined below. +var noValidate = { + validate: false, + filter: false, + autoConvert: false, + removeEmptyStrings: false, + getAutoValues: false +}; var noValidateMulti = _.extend(noValidate, { multi: true }); Migrations.add('board-background-color', function() { -- cgit v1.2.3-1-g7c22