Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Prettier & eslint project style update | Justin Reynolds | 2019-06-28 | 1 | -8/+1 |
| | |||||
* | Add createdAt and modifiedAt to all collections | Justin Reynolds | 2019-06-27 | 1 | -18/+55 |
| | |||||
* | Improve wekan performance #837 | maulal | 2017-02-22 | 1 | -0/+3 |
| | |||||
* | Models: Replace before.insert with autoValues | Alexander Sulfrian | 2016-06-03 | 1 | -4/+5 |
| | | | | | | | | 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. | ||||
* | Centralize all mutations at the model level | Maxime Quandalle | 2015-09-08 | 1 | -0/+34 |
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. |