summaryrefslogtreecommitdiffstats
path: root/models/attachments.js
Commit message (Collapse)AuthorAgeFilesLines
* Fix lint errors.Lauri Ojansivu2018-09-161-6/+6
|
* Remove attachment activityAngelo Gallarello2018-08-161-0/+7
|
* Fix lint errors back to eslint requirements.Lauri Ojansivu2018-05-181-79/+79
|
* Fix lint errors. Update changelog.Lauri Ojansivu2018-01-251-75/+78
|
* Meteor 1.6.0.1, Node 8.9.3, NPM 5.5.1, fibers 2.0.0Lauri Ojansivu2018-01-221-0/+4
|
* Fix lint errorsGhassen Rjab2017-09-021-2/+3
|
* Add source field to imported attachmentsGhassen Rjab2017-09-021-8/+17
| | | We use this field to prevent adding attachments' related activities automatically only. Then this field will be removed.
* use beforeWrite method of CollectionFS instead of collection-hooksGhassen Rjab2017-08-311-18/+18
|
* Fix files access bugGhassen Rjab2017-07-301-12/+6
|
* Update some meta-dataMaxime Quandalle2016-01-021-1/+1
| | | | | | New site url New contact email New year!
* Partially revert aae5030Maxime Quandalle2015-12-241-1/+1
| | | | | | | As discussed in #370 and announced in the official Eslint-meteor plugin repository (https://github.com/dferber90/eslint-plugin-meteor), it is recommended to not use this plugin anymore has the author has it is currently broken and the author has abandoned it.
* Add eslint-plugin-meteorDominik Ferber2015-10-271-1/+1
| | | | | | | | Add rules for eslint-plugin-meteor. Use local version of eslint and eslint-plugin-meteor, instead of relying on global versions. Ensures consistent versions of eslint and eslint-plugin-meteor for all developers.
* Centralize all mutations at the model levelMaxime Quandalle2015-09-081-0/+79
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.