wekan/client/components
Maxime Quandalle d5eec54c72 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.
2015-08-23 11:11:03 +02:00
..
activities Fix card attachments 2015-06-13 15:04:55 +02:00
boards Start the migration from iron-router to flow-router 2015-08-23 11:11:03 +02:00
cards Switch the font to roboto 2015-08-20 15:59:00 +02:00
forms Work on the card activities and comments 2015-06-12 17:48:15 +02:00
lists Start the migration from iron-router to flow-router 2015-08-23 11:11:03 +02:00
main Start the migration from iron-router to flow-router 2015-08-23 11:11:03 +02:00
mixins Switch the font to roboto 2015-08-20 15:59:00 +02:00
sidebar Start the migration from iron-router to flow-router 2015-08-23 11:11:03 +02:00
users Start the migration from iron-router to flow-router 2015-08-23 11:11:03 +02:00