Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Fixed #2338 -> Slow opening of big boards with too many archived items | wekan | 2019-05-13 | 1 | -47/+49 |
| | |||||
* | remove feature | guillaume | 2019-04-23 | 1 | -6/+22 |
| | |||||
* | Add popup menu and archive action | Andrés Manelli | 2018-02-01 | 1 | -0/+11 |
| | |||||
* | Update translation source file | Maxime Quandalle | 2015-09-01 | 1 | -5/+5 |
| | |||||
* | Hide feature non-member users can't use | Maxime Quandalle | 2015-08-28 | 1 | -8/+10 |
| | | | | | Fixes #206 Fixes #244 | ||||
* | Start the migration from iron-router to flow-router | Maxime Quandalle | 2015-08-23 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | 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. | ||||
* | Implement list restoration | Maxime Quandalle | 2015-08-22 | 1 | -11/+24 |
| | |||||
* | Warn if the user try to restore a card in an archived list | Maxime Quandalle | 2015-08-20 | 1 | -0/+2 |
| | |||||
* | Add a UI to restore archived cards | Maxime Quandalle | 2015-06-07 | 1 | -0/+10 |