Commit graph

1367 commits

Author SHA1 Message Date
Xavier Priour
ec304de811 Import board: check json structure before importing 2015-10-19 12:41:56 +02:00
Xavier Priour
456674f111 Import board: set proper color and modifiedAt dates 2015-10-19 11:46:04 +02:00
Xavier Priour
4540bd36c4 Import board: import comments and log activities 2015-10-19 00:59:50 +02:00
Xavier Priour
469d47cd9f Import board: create board, lists, and cards 2015-10-18 01:02:44 +02:00
Xavier Priour
595d5f97ac Import board: now proper createdAt dates 2015-10-17 19:29:25 +02:00
Xavier Priour
468694a84c Import board: added UI 2015-10-17 18:00:46 +02:00
Maxime Quandalle
6dedf673d5 Prevent duplicate board labels
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.
2015-10-16 17:49:25 +02:00
Maxime Quandalle
944a1065d3 Add some ESLint rules and fix some related issues 2015-10-14 23:50:12 +02:00
Maxime Quandalle
43de3b8a01 Prevent dublicated empty labels of the same color 2015-10-14 23:40:27 +02:00
Xavier Priour
b670a1ab36 Import single card: proper error handling 2015-10-14 23:23:17 +02:00
Xavier Priour
7d57ce896b Import single card: create an 'importCard' activity entry 2015-10-14 23:23:16 +02:00
Xavier Priour
4b99ce2aa2 Import single card: check user authorized 2015-10-14 23:23:16 +02:00
Xavier Priour
81bd551137 Import single card: now uses historical dates 2015-10-14 23:23:16 +02:00
Xavier Priour
d8892d6408 Import single card: refactor to meteor method 2015-10-14 23:23:16 +02:00
Xavier Priour
7e64c22c1a Import single card: archived card 2015-10-14 23:23:16 +02:00
Xavier Priour
68518f5497 Import single card: map labels 2015-10-14 23:23:16 +02:00
Maxime Quandalle
45b662a1dd Centralize all mutations at the model level
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.
2015-09-08 20:19:42 +02:00