summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAlexander Sulfrian <alexander.sulfrian@fu-berlin.de>2016-05-31 21:32:08 +0200
committerAlexander Sulfrian <alexander.sulfrian@fu-berlin.de>2016-06-03 03:56:38 +0200
commitb9883a8e244d21f7caf00a794371dbe6b2e4e2ad (patch)
tree62e3da45afb137921857a81023f303abf8bd12da
parent18b1573b25b5f387c42071d2aca0ff8b78f54a3e (diff)
downloadwekan-b9883a8e244d21f7caf00a794371dbe6b2e4e2ad.tar.gz
wekan-b9883a8e244d21f7caf00a794371dbe6b2e4e2ad.tar.bz2
wekan-b9883a8e244d21f7caf00a794371dbe6b2e4e2ad.zip
Remove duplicated logic
The duplicated logic was nessessary because the before.insert hook was not called before validation, when inserting was initiated on the server. Using autoValues fixed this problem.
-rw-r--r--models/users.js7
1 files changed, 0 insertions, 7 deletions
diff --git a/models/users.js b/models/users.js
index 5641ec9b..b56fd2ab 100644
--- a/models/users.js
+++ b/models/users.js
@@ -404,13 +404,6 @@ if (Meteor.isServer) {
title,
boardId,
userId: ExampleBoard.userId,
-
- // XXX Not certain this is a bug, but we except these fields get
- // inserted by the Lists.before.insert collection-hook. Since this
- // hook is not called in this case, we have to dublicate the logic and
- // set them here.
- archived: false,
- createdAt: new Date(),
};
Lists.insert(list);