summaryrefslogtreecommitdiffstats
path: root/client/components/lists
diff options
context:
space:
mode:
authorMaxime Quandalle <maxime@quandalle.com>2015-08-22 22:59:03 +0200
committerMaxime Quandalle <maxime@quandalle.com>2015-08-23 11:11:03 +0200
commitd5eec54c72b755522addc4a839810971ba24f813 (patch)
treeb3f9c1bfde7f4ebd9d2ddca54afa67783c19d983 /client/components/lists
parentf315ee443061c916dc55b291bfe79503fa5e952f (diff)
downloadwekan-d5eec54c72b755522addc4a839810971ba24f813.tar.gz
wekan-d5eec54c72b755522addc4a839810971ba24f813.tar.bz2
wekan-d5eec54c72b755522addc4a839810971ba24f813.zip
Start the migration from iron-router to flow-router
Motivations: * Iron-Router foces us to use Tracker.nonreactive black magic in order to avoid un-necessary re-renders; * There is a community consensus (supported by some MDG members) that the flow-router API is easier to reason about; * The useraccounts now supports flow router (that was a blocking element when I considered the switch ~3months ago) On the server we use the Picker router, as encouraged by the Kadira team (which develop both Flow and Picker routers). In the current state of things there are some bugs related to the missing Loading architecure. Previously onRendered callback where always called when the data the component needed was available, now we have to handle this ourselves, which we will in a following commit.
Diffstat (limited to 'client/components/lists')
-rw-r--r--client/components/lists/main.js2
1 files changed, 1 insertions, 1 deletions
diff --git a/client/components/lists/main.js b/client/components/lists/main.js
index c4e38c46..e6491f0a 100644
--- a/client/components/lists/main.js
+++ b/client/components/lists/main.js
@@ -21,7 +21,7 @@ BlazeComponent.extendComponent({
// comment below provides further details.
onRendered: function() {
var self = this;
- if (! Meteor.userId() || ! Meteor.user().isBoardMember())
+ if (! Meteor.user() || ! Meteor.user().isBoardMember())
return;
var boardComponent = self.componentParent();