mfAll.js - creationTime replaced with null

[1u]

(this is not new..) Is this done intentionally?

here's a part of our commit (https://github.com/schuel/hmmm/commit/f2f9e67d390a4a276051ea0aba3b9d4397137adb) where we added new mfAll.js file:

@@ -15394,7 +15493,7 @@ mfPkg.syncAll({

     "course.edit.categories": {
       "_id": "3ZzKKLEndL6pdBXLH",
       "key": "course.edit.categories",
       "lang": "en",
       "text": "Categories:",
-      "ctime": "2015-12-24T00:01:14.000Z",
-      "mtime": "2015-12-24T00:01:14.000Z",
+      "ctime": null,
+      "mtime": 1463453680000,
       "revisionId": "zJhXqmN58ZnaKFYZY",
       "file": "client/views/courses/details/course.edit.html",
-      "line": 45,
+      "line": 70,
       "template": "course_edit"
     },
     "course.edit.description": {
@@ -15284,11 +15359,11 @@ mfPkg.syncAll({
       "key": "course.edit.description",
       "lang": "en",
       "text": "Description:",
-      "ctime": "2015-12-24T00:01:14.000Z",
-      "mtime": "2015-12-24T00:01:14.000Z",
+      "ctime": null,
+      "mtime": 1463453680000,
       "revisionId": "bokshs5gGGb6LosmH",
       "file": "client/views/courses/details/course.edit.html",
-      "line": 13,
+      "line": 22,
       "template": "course_edit"
     },

[gadicc]

That's a bug, but fortunately very low impact... I don't think we actually use the ctime anywhere... definitely not if the mtime exists also.