Commit graph

256 commits

Author SHA1 Message Date
Maxime Quandalle
f3fc154eb0 Re-implement label deletion
This was not ported during v0.9 re-factor.

Fixes #322
2015-10-20 19:07:24 +02:00
Xavier Priour
8e0ad91191 Import board: map team permission, and refactor code to share with card import 2015-10-19 20:14:29 +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
43de3b8a01 Prevent dublicated empty labels of the same color 2015-10-14 23:40:27 +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
Renamed from collections/boards.js (Browse further)