From 050164f1a5af0d51d4e211c35976e823ab3dbe93 Mon Sep 17 00:00:00 2001 From: "Alex A. Naanou" Date: Sat, 23 Dec 2017 01:27:25 +0300 Subject: [PATCH] notes... Signed-off-by: Alex A. Naanou --- ui (gen4)/features/collections.js | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ui (gen4)/features/collections.js b/ui (gen4)/features/collections.js index 4e0dcdad..1af81edf 100755 --- a/ui (gen4)/features/collections.js +++ b/ui (gen4)/features/collections.js @@ -783,12 +783,12 @@ var CollectionActions = actions.Actions({ // // NOTE: Currently these are sync, and sequencing collections // operations happens automatically as everything uses - // .ensureCollection(..)... + // .ensureCollection(..) internally... // to explecitly sequence code do: // .collect(..) // .ensureCollection(..) // .then(function(){ - // // this is run after .collect(..) + // // this is run strictly after .collect(..) // ... // }) // NOTE: see .ensureCollection(..) for more details... @@ -1126,7 +1126,7 @@ var CollectionActions = actions.Actions({ // in to maintain the correct order when merging... (XXX) // NOTE: currently this only stores title and data, it is the // responsibility of extending features to store their specific - // data in collections... + // stuff in collections... // XXX is this the right way to go??? // NOTE: .chnages are handled separately in feature .handlers... json: [function(mode){ return function(res){