summaryrefslogtreecommitdiffstats
path: root/models/cards.js
Commit message (Collapse)AuthorAgeFilesLines
* direct hook to bypass the checking step with API requestzago2017-07-191-130/+167
|
* fixe traviszago2017-07-071-18/+18
|
* checking the authorId when adding cardzago2017-07-071-15/+22
|
* fixe errorzago2017-06-291-3/+3
|
* linebreaker fixingzago2017-06-291-24/+23
|
* adding a put method to update a cardzago2017-06-291-0/+30
|
* Added readonly user access to cardsmayjs2017-05-151-2/+2
|
* add token authentication, only admin can use apihuneau romain2017-05-111-0/+4
|
* REST API - Meteor 1.4 - first step issueLauri Ojansivu2017-04-271-19/+79
|
* Bug: orphan documents were created when cards were deletedmaulal2017-02-251-0/+10
|
* Improve wekan performance #837maulal2017-02-221-1/+1
|
* [BUG] Bug when we're removing user from board that generate activity for all ↵Florent MONTHEL2017-02-211-7/+10
| | | | the card of the board
* Add checklist featurelksime2017-01-201-0/+30
|
* Adds start and due date to cards model.shoetten2016-11-211-0/+24
|
* Add MongoDB indexesMaxime Quandalle2016-07-181-0/+6
| | | | | | | These indexes will optimize the queries that are used in the board and card views. Fixes #524.
* Models: Replace before.insert with autoValuesAlexander Sulfrian2016-06-031-12/+20
| | | | | | | | The before.insert hooks have the problem, that they are executed in a different order if called from the client or from the server. If called from the client, the before.insert hook is called before validation of the schema, but if called from the server, the validation is called first and fails.
* Add notification, allow watch boards / lists / cardsLiming Xie2016-01-051-5/+1
|
* Import attachmentsXavier Priour2015-11-161-1/+4
|
* Import single card: archived cardXavier Priour2015-10-141-2/+3
|
* Centralize all mutations at the model levelMaxime Quandalle2015-09-081-0/+291
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.