@webresto/graphql 1.3.2 → 1.3.3

package/test/fixture/config/http.js

@@ -1,93 +1,93 @@
-/**
- * HTTP Server Settings
- * (sails.config.http)
- *
- * Configuration for the underlying HTTP server in Sails.
- * Only applies to HTTP requests (not WebSockets)
- *
- * For more information on configuration, check out:
- * http://sailsjs.org/#!/documentation/reference/sails.config/sails.config.http.html
- */
-
-module.exports.http = {
-
-  /****************************************************************************
-  *                                                                           *
-  * Express middleware to use for every Sails request. To add custom          *
-  * middleware to the mix, add a function to the middleware config object and *
-  * add its key to the "order" array. The $custom key is reserved for         *
-  * backwards-compatibility with Sails v0.9.x apps that use the               *
-  * `customMiddleware` config option.                                         *
-  *                                                                           *
-  ****************************************************************************/
-
-  middleware: {
-
-  /***************************************************************************
-  *                                                                          *
-  * The order in which middleware should be run for HTTP request. (the Sails *
-  * router is invoked by the "router" middleware below.)                     *
-  *                                                                          *
-  ***************************************************************************/
-
-    // order: [
-    //   'startRequestTimer',
-    //   'cookieParser',
-    //   'session',
-    //   'myRequestLogger',
-    //   'bodyParser',
-    //   'handleBodyParserError',
-    //   'compress',
-    //   'methodOverride',
-    //   'poweredBy',
-    //   '$custom',
-    //   'router',
-    //   'www',
-    //   'favicon',
-    //   '404',
-    //   '500'
-    // ],
-
-  /****************************************************************************
-  *                                                                           *
-  * Example custom middleware; logs each request to the console.              *
-  *                                                                           *
-  ****************************************************************************/
-
-    // myRequestLogger: function (req, res, next) {
-    //     console.log("Requested :: ", req.method, req.url);
-    //     return next();
-    // }
-
-
-  /***************************************************************************
-  *                                                                          *
-  * The body parser that will handle incoming multipart HTTP requests. By    *
-  * default as of v0.10, Sails uses                                          *
-  * [skipper](http://github.com/balderdashy/skipper). See                    *
-  * http://www.senchalabs.org/connect/multipart.html for other options.      *
-  *                                                                          *
-  * Note that Sails uses an internal instance of Skipper by default; to      *
-  * override it and specify more options, make sure to "npm install skipper" *
-  * in your project first.  You can also specify a different body parser or  *
-  * a custom function with req, res and next parameters (just like any other *
-  * middleware function).                                                    *
-  *                                                                          *
-  ***************************************************************************/
-
-    // bodyParser: require('skipper')({strict: true})
-
-  },
-
-  /***************************************************************************
-  *                                                                          *
-  * The number of seconds to cache flat files on disk being served by        *
-  * Express static middleware (by default, these files are in `.tmp/public`) *
-  *                                                                          *
-  * The HTTP static cache is only active in a 'production' environment,      *
-  * since that's the only time Express will cache flat-files.                *
-  *                                                                          *
-  ***************************************************************************/
-
-  // cache: 31557600000
-};
+/**
+ * HTTP Server Settings
+ * (sails.config.http)
+ *
+ * Configuration for the underlying HTTP server in Sails.
+ * Only applies to HTTP requests (not WebSockets)
+ *
+ * For more information on configuration, check out:
+ * http://sailsjs.org/#!/documentation/reference/sails.config/sails.config.http.html
+ */
+
+module.exports.http = {
+
+  /****************************************************************************
+  *                                                                           *
+  * Express middleware to use for every Sails request. To add custom          *
+  * middleware to the mix, add a function to the middleware config object and *
+  * add its key to the "order" array. The $custom key is reserved for         *
+  * backwards-compatibility with Sails v0.9.x apps that use the               *
+  * `customMiddleware` config option.                                         *
+  *                                                                           *
+  ****************************************************************************/
+
+  middleware: {
+
+  /***************************************************************************
+  *                                                                          *
+  * The order in which middleware should be run for HTTP request. (the Sails *
+  * router is invoked by the "router" middleware below.)                     *
+  *                                                                          *
+  ***************************************************************************/
+
+    // order: [
+    //   'startRequestTimer',
+    //   'cookieParser',
+    //   'session',
+    //   'myRequestLogger',
+    //   'bodyParser',
+    //   'handleBodyParserError',
+    //   'compress',
+    //   'methodOverride',
+    //   'poweredBy',
+    //   '$custom',
+    //   'router',
+    //   'www',
+    //   'favicon',
+    //   '404',
+    //   '500'
+    // ],
+
+  /****************************************************************************
+  *                                                                           *
+  * Example custom middleware; logs each request to the console.              *
+  *                                                                           *
+  ****************************************************************************/
+
+    // myRequestLogger: function (req, res, next) {
+    //     console.log("Requested :: ", req.method, req.url);
+    //     return next();
+    // }
+
+
+  /***************************************************************************
+  *                                                                          *
+  * The body parser that will handle incoming multipart HTTP requests. By    *
+  * default as of v0.10, Sails uses                                          *
+  * [skipper](http://github.com/balderdashy/skipper). See                    *
+  * http://www.senchalabs.org/connect/multipart.html for other options.      *
+  *                                                                          *
+  * Note that Sails uses an internal instance of Skipper by default; to      *
+  * override it and specify more options, make sure to "npm install skipper" *
+  * in your project first.  You can also specify a different body parser or  *
+  * a custom function with req, res and next parameters (just like any other *
+  * middleware function).                                                    *
+  *                                                                          *
+  ***************************************************************************/
+
+    // bodyParser: require('skipper')({strict: true})
+
+  },
+
+  /***************************************************************************
+  *                                                                          *
+  * The number of seconds to cache flat files on disk being served by        *
+  * Express static middleware (by default, these files are in `.tmp/public`) *
+  *                                                                          *
+  * The HTTP static cache is only active in a 'production' environment,      *
+  * since that's the only time Express will cache flat-files.                *
+  *                                                                          *
+  ***************************************************************************/
+
+  // cache: 31557600000
+};

package/test/fixture/config/i18n.js

@@ -1,57 +1,57 @@
-/**
- * Internationalization / Localization Settings
- * (sails.config.i18n)
- *
- * If your app will touch people from all over the world, i18n (or internationalization)
- * may be an important part of your international strategy.
- *
- *
- * For more informationom i18n in Sails, check out:
- * http://sailsjs.org/#!/documentation/concepts/Internationalization
- *
- * For a complete list of i18n options, see:
- * https://github.com/mashpie/i18n-node#list-of-configuration-options
- *
- *
- */
-
-module.exports.i18n = {
-
-  /***************************************************************************
-  *                                                                          *
-  * Which locales are supported?                                             *
-  *                                                                          *
-  ***************************************************************************/
-
-  // locales: ['en', 'es', 'fr', 'de'],
-
-  /****************************************************************************
-  *                                                                           *
-  * What is the default locale for the site? Note that this setting will be   *
-  * overridden for any request that sends an "Accept-Language" header (i.e.   *
-  * most browsers), but it's still useful if you need to localize the         *
-  * response for requests made by non-browser clients (e.g. cURL).            *
-  *                                                                           *
-  ****************************************************************************/
-
-  // defaultLocale: 'en',
-
-  /****************************************************************************
-  *                                                                           *
-  * Automatically add new keys to locale (translation) files when they are    *
-  * encountered during a request?                                             *
-  *                                                                           *
-  ****************************************************************************/
-
-  // updateFiles: false,
-
-  /****************************************************************************
-  *                                                                           *
-  * Path (relative to app root) of directory to store locale (translation)    *
-  * files in.                                                                 *
-  *                                                                           *
-  ****************************************************************************/
-
-  // localesDirectory: '/config/locales'
-
-};
+/**
+ * Internationalization / Localization Settings
+ * (sails.config.i18n)
+ *
+ * If your app will touch people from all over the world, i18n (or internationalization)
+ * may be an important part of your international strategy.
+ *
+ *
+ * For more informationom i18n in Sails, check out:
+ * http://sailsjs.org/#!/documentation/concepts/Internationalization
+ *
+ * For a complete list of i18n options, see:
+ * https://github.com/mashpie/i18n-node#list-of-configuration-options
+ *
+ *
+ */
+
+module.exports.i18n = {
+
+  /***************************************************************************
+  *                                                                          *
+  * Which locales are supported?                                             *
+  *                                                                          *
+  ***************************************************************************/
+
+  // locales: ['en', 'es', 'fr', 'de'],
+
+  /****************************************************************************
+  *                                                                           *
+  * What is the default locale for the site? Note that this setting will be   *
+  * overridden for any request that sends an "Accept-Language" header (i.e.   *
+  * most browsers), but it's still useful if you need to localize the         *
+  * response for requests made by non-browser clients (e.g. cURL).            *
+  *                                                                           *
+  ****************************************************************************/
+
+  // defaultLocale: 'en',
+
+  /****************************************************************************
+  *                                                                           *
+  * Automatically add new keys to locale (translation) files when they are    *
+  * encountered during a request?                                             *
+  *                                                                           *
+  ****************************************************************************/
+
+  // updateFiles: false,
+
+  /****************************************************************************
+  *                                                                           *
+  * Path (relative to app root) of directory to store locale (translation)    *
+  * files in.                                                                 *
+  *                                                                           *
+  ****************************************************************************/
+
+  // localesDirectory: '/config/locales'
+
+};

package/test/fixture/config/log.js

@@ -1,29 +1,29 @@
-/**
- * Built-in Log Configuration
- * (sails.config.log)
- *
- * Configure the log level for your app, as well as the transport
- * (Underneath the covers, Sails uses Winston for logging, which
- * allows for some pretty neat custom transports/adapters for log messages)
- *
- * For more information on the Sails logger, check out:
- * http://sailsjs.org/#!/documentation/concepts/Logging
- */
-
-module.exports.log = {
-
-  /***************************************************************************
-  *                                                                          *
-  * Valid `level` configs: i.e. the minimum log level to capture with        *
-  * sails.log.*()                                                            *
-  *                                                                          *
-  * The order of precedence for log levels from lowest to highest is:        *
-  * silly, verbose, info, debug, warn, error                                 *
-  *                                                                          *
-  * You may also set the level to "silent" to suppress all logs.             *
-  *                                                                          *
-  ***************************************************************************/
-
-   level: 'verbose'
-
-};
+/**
+ * Built-in Log Configuration
+ * (sails.config.log)
+ *
+ * Configure the log level for your app, as well as the transport
+ * (Underneath the covers, Sails uses Winston for logging, which
+ * allows for some pretty neat custom transports/adapters for log messages)
+ *
+ * For more information on the Sails logger, check out:
+ * http://sailsjs.org/#!/documentation/concepts/Logging
+ */
+
+module.exports.log = {
+
+  /***************************************************************************
+  *                                                                          *
+  * Valid `level` configs: i.e. the minimum log level to capture with        *
+  * sails.log.*()                                                            *
+  *                                                                          *
+  * The order of precedence for log levels from lowest to highest is:        *
+  * silly, verbose, info, debug, warn, error                                 *
+  *                                                                          *
+  * You may also set the level to "silent" to suppress all logs.             *
+  *                                                                          *
+  ***************************************************************************/
+
+   level: 'debug'
+
+};

package/test/fixture/config/models.js

@@ -1,9 +1,9 @@
-module.exports.models = {
-   migrate: 'drop',
-   attributes: {
-      id: { type: 'number', autoIncrement: true, },
-      createdAt: { type: 'number', autoCreatedAt: true, },
-      updatedAt: { type: 'number', autoUpdatedAt: true, }
-    },
-    
+module.exports.models = {
+   migrate: 'drop',
+   attributes: {
+      id: { type: 'number', autoIncrement: true, },
+      createdAt: { type: 'number', autoCreatedAt: true, },
+      updatedAt: { type: 'number', autoUpdatedAt: true, }
+    },
+    
 };

package/test/fixture/config/modulemanager.js

@@ -1,22 +1,22 @@
-module.exports.modulemanager = {
-    navbar: [
-        {
-            id: "1",
-            name: "Мои модули",
-            link: `/admin/modules/my`,
-            icon: "home"
-        },
-        {
-            id: "2",
-            name: "Обновления",
-            link: `/admin/modules/updates`,
-            icon: "cloud-download-alt"
-        },
-        {
-            id: "3",
-            name: "Маркетплейс",
-            link: `/admin/modules/market`,
-            icon: "shopping-cart"
-        }
-    ]
-}
+module.exports.modulemanager = {
+    navbar: [
+        {
+            id: "1",
+            name: "Мои модули",
+            link: `/admin/modules/my`,
+            icon: "home"
+        },
+        {
+            id: "2",
+            name: "Обновления",
+            link: `/admin/modules/updates`,
+            icon: "cloud-download-alt"
+        },
+        {
+            id: "3",
+            name: "Маркетплейс",
+            link: `/admin/modules/market`,
+            icon: "shopping-order"
+        }
+    ]
+}

package/test/fixture/config/policies.js

@@ -1,51 +1,51 @@
-/**
- * Policy Mappings
- * (sails.config.policies)
- *
- * Policies are simple functions which run **before** your controllers.
- * You can apply one or more policies to a given controller, or protect
- * its actions individually.
- *
- * Any policy file (e.g. `api/policies/authenticated.js`) can be accessed
- * below by its filename, minus the extension, (e.g. "authenticated")
- *
- * For more information on how policies work, see:
- * http://sailsjs.org/#!/documentation/concepts/Policies
- *
- * For more information on configuring policies, check out:
- * http://sailsjs.org/#!/documentation/reference/sails.config/sails.config.policies.html
- */
-
-
-module.exports.policies = {
-
-  /***************************************************************************
-  *                                                                          *
-  * Default policy for all controllers and actions (`true` allows public     *
-  * access)                                                                  *
-  *                                                                          *
-  ***************************************************************************/
-
-  // '*': true,
-
-  /***************************************************************************
-  *                                                                          *
-  * Here's an example of mapping some policies to run before a controller    *
-  * and its actions                                                          *
-  *                                                                          *
-  ***************************************************************************/
-	// RabbitController: {
-
-		// Apply the `false` policy as the default for all of RabbitController's actions
-		// (`false` prevents all access, which ensures that nothing bad happens to our rabbits)
-		// '*': false,
-
-		// For the action `nurture`, apply the 'isRabbitMother' policy
-		// (this overrides `false` above)
-		// nurture	: 'isRabbitMother',
-
-		// Apply the `isNiceToAnimals` AND `hasRabbitFood` policies
-		// before letting any users feed our rabbits
-		// feed : ['isNiceToAnimals', 'hasRabbitFood']
-	// }
-};
+/**
+ * Policy Mappings
+ * (sails.config.policies)
+ *
+ * Policies are simple functions which run **before** your controllers.
+ * You can apply one or more policies to a given controller, or protect
+ * its actions individually.
+ *
+ * Any policy file (e.g. `api/policies/authenticated.js`) can be accessed
+ * below by its filename, minus the extension, (e.g. "authenticated")
+ *
+ * For more information on how policies work, see:
+ * http://sailsjs.org/#!/documentation/concepts/Policies
+ *
+ * For more information on configuring policies, check out:
+ * http://sailsjs.org/#!/documentation/reference/sails.config/sails.config.policies.html
+ */
+
+
+module.exports.policies = {
+
+  /***************************************************************************
+  *                                                                          *
+  * Default policy for all controllers and actions (`true` allows public     *
+  * access)                                                                  *
+  *                                                                          *
+  ***************************************************************************/
+
+  // '*': true,
+
+  /***************************************************************************
+  *                                                                          *
+  * Here's an example of mapping some policies to run before a controller    *
+  * and its actions                                                          *
+  *                                                                          *
+  ***************************************************************************/
+	// RabbitController: {
+
+		// Apply the `false` policy as the default for all of RabbitController's actions
+		// (`false` prevents all access, which ensures that nothing bad happens to our rabbits)
+		// '*': false,
+
+		// For the action `nurture`, apply the 'isRabbitMother' policy
+		// (this overrides `false` above)
+		// nurture	: 'isRabbitMother',
+
+		// Apply the `isNiceToAnimals` AND `hasRabbitFood` policies
+		// before letting any users feed our rabbits
+		// feed : ['isNiceToAnimals', 'hasRabbitFood']
+	// }
+};

package/test/fixture/config/routes.js

@@ -1,49 +1,49 @@
-/**
- * Route Mappings
- * (sails.config.routes)
- *
- * Your routes map URLs to views and controllers.
- *
- * If Sails receives a URL that doesn't match any of the routes below,
- * it will check for matching files (images, scripts, stylesheets, etc.)
- * in your assets directory.  e.g. `http://localhost:1337/images/foo.jpg`
- * might match an image file: `/assets/images/foo.jpg`
- *
- * Finally, if those don't match either, the default 404 handler is triggered.
- * See `api/responses/notFound.js` to adjust your app's 404 logic.
- *
- * Note: Sails doesn't ACTUALLY serve stuff from `assets`-- the default Gruntfile in Sails copies
- * flat files from `assets` to `.tmp/public`.  This allows you to do things like compile LESS or
- * CoffeeScript for the front-end.
- *
- * For more information on configuring custom routes, check out:
- * http://sailsjs.org/#!/documentation/concepts/Routes/RouteTargetSyntax.html
- */
-
-module.exports.routes = {
-
-  /***************************************************************************
-  *                                                                          *
-  * Make the view located at `views/homepage.ejs` (or `views/homepage.jade`, *
-  * etc. depending on your default view engine) your home page.              *
-  *                                                                          *
-  * (Alternatively, remove this and add an `index.html` file in your         *
-  * `assets` directory)                                                      *
-  *                                                                          *
-  ***************************************************************************/
-
-  '/': {
-    view: 'homepage'
-  }
-
-  /***************************************************************************
-  *                                                                          *
-  * Custom routes here...                                                    *
-  *                                                                          *
-  * If a request to a URL doesn't match any of the custom routes above, it   *
-  * is matched against Sails route blueprints. See `config/blueprints.js`    *
-  * for configuration options and examples.                                  *
-  *                                                                          *
-  ***************************************************************************/
-
-};
+/**
+ * Route Mappings
+ * (sails.config.routes)
+ *
+ * Your routes map URLs to views and controllers.
+ *
+ * If Sails receives a URL that doesn't match any of the routes below,
+ * it will check for matching files (images, scripts, stylesheets, etc.)
+ * in your assets directory.  e.g. `http://localhost:1337/images/foo.jpg`
+ * might match an image file: `/assets/images/foo.jpg`
+ *
+ * Finally, if those don't match either, the default 404 handler is triggered.
+ * See `api/responses/notFound.js` to adjust your app's 404 logic.
+ *
+ * Note: Sails doesn't ACTUALLY serve stuff from `assets`-- the default Gruntfile in Sails copies
+ * flat files from `assets` to `.tmp/public`.  This allows you to do things like compile LESS or
+ * CoffeeScript for the front-end.
+ *
+ * For more information on configuring custom routes, check out:
+ * http://sailsjs.org/#!/documentation/concepts/Routes/RouteTargetSyntax.html
+ */
+
+module.exports.routes = {
+
+  /***************************************************************************
+  *                                                                          *
+  * Make the view located at `views/homepage.ejs` (or `views/homepage.jade`, *
+  * etc. depending on your default view engine) your home page.              *
+  *                                                                          *
+  * (Alternatively, remove this and add an `index.html` file in your         *
+  * `assets` directory)                                                      *
+  *                                                                          *
+  ***************************************************************************/
+
+  '/': {
+    view: 'homepage'
+  }
+
+  /***************************************************************************
+  *                                                                          *
+  * Custom routes here...                                                    *
+  *                                                                          *
+  * If a request to a URL doesn't match any of the custom routes above, it   *
+  * is matched against Sails route blueprints. See `config/blueprints.js`    *
+  * for configuration options and examples.                                  *
+  *                                                                          *
+  ***************************************************************************/
+
+};