| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151 | /** * Blueprint API Configuration * (sails.config.blueprints) * * These settings are for the global configuration of blueprint routes and * request options (which impact the behavior of blueprint actions). * * You may also override any of these settings on a per-controller basis * by defining a '_config' key in your controller defintion, and assigning it * a configuration object with overrides for the settings in this file. * A lot of the configuration options below affect so-called "CRUD methods", * or your controllers' `find`, `create`, `update`, and `destroy` actions. * * It's important to realize that, even if you haven't defined these yourself, as long as * a model exists with the same name as the controller, Sails will respond with built-in CRUD * logic in the form of a JSON API, including support for sort, pagination, and filtering. * * For more information on the blueprint API, check out: * http://sailsjs.org/#/documentation/reference/blueprint-api * * For more information on the settings in this file, see: * http://sailsjs.org/#/documentation/reference/sails.config/sails.config.blueprints.html * */module.exports.blueprints = {  /***************************************************************************  *                                                                          *  * Action routes speed up the backend development workflow by               *  * eliminating the need to manually bind routes. When enabled, GET, POST,   *  * PUT, and DELETE routes will be generated for every one of a controller's *  * actions.                                                                 *  *                                                                          *  * If an `index` action exists, additional naked routes will be created for *  * it. Finally, all `actions` blueprints support an optional path           *  * parameter, `id`, for convenience.                                        *  *                                                                          *  * `actions` are enabled by default, and can be OK for production--         *  * however, if you'd like to continue to use controller/action autorouting  *  * in a production deployment, you must take great care not to              *  * inadvertently expose unsafe/unintentional controller logic to GET        *  * requests.                                                                *  *                                                                          *  ***************************************************************************/  // actions: true,  /***************************************************************************  *                                                                          *  * RESTful routes (`sails.config.blueprints.rest`)                          *  *                                                                          *  * REST blueprints are the automatically generated routes Sails uses to     *  * expose a conventional REST API on top of a controller's `find`,          *  * `create`, `update`, and `destroy` actions.                               *  *                                                                          *  * For example, a BoatController with `rest` enabled generates the          *  * following routes:                                                        *  * :::::::::::::::::::::::::::::::::::::::::::::::::::::::                  *  *  GET /boat -> BoatController.find                                        *  *  GET /boat/:id -> BoatController.findOne                                 *  *  POST /boat -> BoatController.create                                     *  *  PUT /boat/:id -> BoatController.update                                  *  *  DELETE /boat/:id -> BoatController.destroy                              *  *                                                                          *  * `rest` blueprint routes are enabled by default, and are suitable for use *  * in a production scenario, as long you take standard security precautions *  * (combine w/ policies, etc.)                                              *  *                                                                          *  ***************************************************************************/  // rest: true,  /***************************************************************************  *                                                                          *  * Shortcut routes are simple helpers to provide access to a                *  * controller's CRUD methods from your browser's URL bar. When enabled,     *  * GET, POST, PUT, and DELETE routes will be generated for the              *  * controller's`find`, `create`, `update`, and `destroy` actions.           *  *                                                                          *  * `shortcuts` are enabled by default, but should be disabled in            *  * production.                                                              *  *                                                                          *  ***************************************************************************/  // shortcuts: true,  /***************************************************************************  *                                                                          *  * An optional mount path for all blueprint routes on a controller,         *  * including `rest`, `actions`, and `shortcuts`. This allows you to take    *  * advantage of blueprint routing, even if you need to namespace your API   *  * methods.                                                                 *  *                                                                          *  * (NOTE: This only applies to blueprint autoroutes, not manual routes from *  * `sails.config.routes`)                                                   *  *                                                                          *  ***************************************************************************/  // prefix: '',  /***************************************************************************  *                                                                          *  * Whether to pluralize controller names in blueprint routes.               *  *                                                                          *  * (NOTE: This only applies to blueprint autoroutes, not manual routes from *  * `sails.config.routes`)                                                   *  *                                                                          *  * For example, REST blueprints for `FooController` with `pluralize`        *  * enabled:                                                                 *  * GET /foos/:id?                                                           *  * POST /foos                                                               *  * PUT /foos/:id?                                                           *  * DELETE /foos/:id?                                                        *  *                                                                          *  ***************************************************************************/  // pluralize: false,  /***************************************************************************  *                                                                          *  * Whether the blueprint controllers should populate model fetches with     *  * data from other models which are linked by associations                  *  *                                                                          *  * If you have a lot of data in one-to-many associations, leaving this on   *  * may result in very heavy api calls                                       *  *                                                                          *  ***************************************************************************/  // populate: true,  /****************************************************************************  *                                                                           *  * Whether to run Model.watch() in the find and findOne blueprint actions.   *  * Can be overridden on a per-model basis.                                   *  *                                                                           *  ****************************************************************************/  // autoWatch: true,  /****************************************************************************  *                                                                           *  * The default number of records to show in the response from a "find"       *  * action. Doubles as the default size of populated arrays if populate is    *  * true.                                                                     *  *                                                                           *  ****************************************************************************/  // defaultLimit: 30};
 |