summaryrefslogtreecommitdiffstats
path: root/models
Commit message (Collapse)AuthorAgeFilesLines
...
| * Import board: map team permission, and refactor code to share with card importXavier Priour2015-10-192-132/+80
| |
| * Import board: check json structure before importingXavier Priour2015-10-191-6/+58
| |
| * Import board: set proper color and modifiedAt datesXavier Priour2015-10-191-7/+28
| |
| * Import board: import comments and log activitiesXavier Priour2015-10-191-49/+117
| |
| * Import board: create board, lists, and cardsXavier Priour2015-10-181-13/+66
| |
| * Import board: now proper createdAt datesXavier Priour2015-10-171-0/+73
| |
| * Import board: added UIXavier Priour2015-10-171-5/+20
| |
* | Re-implement label deletionMaxime Quandalle2015-10-201-1/+1
| | | | | | | | | | | | This was not ported during v0.9 re-factor. Fixes #322
* | Prevent duplicate board labelsMaxime Quandalle2015-10-162-42/+31
|/ | | | | | 43de3b8 did prevent empty labels with the same color, but we also want to prevent label with the same non-empty name and same color because the rationale is identical.
* Add some ESLint rules and fix some related issuesMaxime Quandalle2015-10-141-8/+7
|
* Prevent dublicated empty labels of the same colorMaxime Quandalle2015-10-141-5/+14
|
* Import single card: proper error handlingXavier Priour2015-10-141-22/+26
|
* Import single card: create an 'importCard' activity entryXavier Priour2015-10-141-8/+22
|
* Import single card: check user authorizedXavier Priour2015-10-141-10/+16
|
* Import single card: now uses historical datesXavier Priour2015-10-141-11/+20
|
* Import single card: refactor to meteor methodXavier Priour2015-10-141-0/+98
|
* Import single card: archived cardXavier Priour2015-10-141-2/+3
|
* Import single card: map labelsXavier Priour2015-10-141-2/+8
|
* Centralize all mutations at the model levelMaxime Quandalle2015-09-089-0/+1166
This commit uses a new package that I need to document. It tries to solve the long-standing debate in the Meteor community about allow/deny rules versus methods (RPC). This approach gives us both the centralized security rules of allow/deny and the white-list of allowed mutations similarly to Meteor methods. The idea to have static mutation descriptions is also inspired by Facebook's Relay/GraphQL. This will allow the development of a REST API using the high-level methods instead of the MongoDB queries to do the mapping between the HTTP requests and our collections.