@webresto/graphql 1.3.2 → 1.3.3

package/test/fixture/config/session.js

@@ -1,100 +1,100 @@
-/**
- * Session Configuration
- * (sails.config.session)
- *
- * Sails session integration leans heavily on the great work already done by
- * Express, but also unifies Socket.io with the Connect session store. It uses
- * Connect's cookie parser to normalize configuration differences between Express
- * and Socket.io and hooks into Sails' middleware interpreter to allow you to access
- * and auto-save to `req.session` with Socket.io the same way you would with Express.
- *
- * For more information on configuring the session, check out:
- * http://sailsjs.org/#!/documentation/reference/sails.config/sails.config.session.html
- */
-
-module.exports.session = {
-
-  /***************************************************************************
-  *                                                                          *
-  * Session secret is automatically generated when your new app is created   *
-  * Replace at your own risk in production-- you will invalidate the cookies *
-  * of your users, forcing them to log in again.                             *
-  *                                                                          *
-  ***************************************************************************/
-  secret: 'ffbef9b6711dc3130e47e22d46fee23c',
-
-
-  /***************************************************************************
-  *                                                                          *
-  * Set the session cookie expire time The maxAge is set by milliseconds,    *
-  * the example below is for 24 hours                                        *
-  *                                                                          *
-  ***************************************************************************/
-
-  // cookie: {
-  //   maxAge: 24 * 60 * 60 * 1000
-  // },
-
-  /***************************************************************************
-  *                                                                          *
-  * Uncomment the following lines to set up a Redis session store that can   *
-  * be shared across multiple Sails.js servers.                              *
-  *                                                                          *
-  * Requires connect-redis (https://www.npmjs.com/package/connect-redis)     *
-  *                                                                          *
-  ***************************************************************************/
-
-  // adapter: 'redis',
-
-  /***************************************************************************
-  *                                                                          *
-  * The following values are optional, if no options are set a redis         *
-  * instance running on localhost is expected. Read more about options at:   *
-  *                                                                          *
-  * https://github.com/visionmedia/connect-redis                             *
-  *                                                                          *
-  ***************************************************************************/
-
-  // host: 'localhost',
-  // port: 6379,
-  // ttl: <redis session TTL in seconds>,
-  // db: 0,
-  // pass: <redis auth password>,
-  // prefix: 'sess:',
-
-
-  /***************************************************************************
-  *                                                                          *
-  * Uncomment the following lines to set up a MongoDB session store that can *
-  * be shared across multiple Sails.js servers.                              *
-  *                                                                          *
-  * Requires connect-mongo (https://www.npmjs.com/package/connect-mongo)     *
-  * Use version 0.8.2 with Node version <= 0.12                              *
-  * Use the latest version with Node >= 4.0                                  *
-  *                                                                          *
-  ***************************************************************************/
-
-  // adapter: 'mongo',
-  // url: 'mongodb://user:password@localhost:27017/dbname', // user, password and port optional
-
-  /***************************************************************************
-  *                                                                          *
-  * Optional Values:                                                         *
-  *                                                                          *
-  * See https://github.com/kcbanner/connect-mongo for more                   *
-  * information about connect-mongo options.                                 *
-  *                                                                          *
-  * See http://bit.ly/mongooptions for more information about options        *
-  * available in `mongoOptions`                                              *
-  *                                                                          *
-  ***************************************************************************/
-
-  // collection: 'sessions',
-  // stringify: true,
-  // mongoOptions: {
-  //   server: {
-  //     ssl: true
-  //   }
-  // }
-
-};
+/**
+ * Session Configuration
+ * (sails.config.session)
+ *
+ * Sails session integration leans heavily on the great work already done by
+ * Express, but also unifies Socket.io with the Connect session store. It uses
+ * Connect's cookie parser to normalize configuration differences between Express
+ * and Socket.io and hooks into Sails' middleware interpreter to allow you to access
+ * and auto-save to `req.session` with Socket.io the same way you would with Express.
+ *
+ * For more information on configuring the session, check out:
+ * http://sailsjs.org/#!/documentation/reference/sails.config/sails.config.session.html
+ */
+
+module.exports.session = {
+
+  /***************************************************************************
+  *                                                                          *
+  * Session secret is automatically generated when your new app is created   *
+  * Replace at your own risk in production-- you will invalidate the cookies *
+  * of your users, forcing them to log in again.                             *
+  *                                                                          *
+  ***************************************************************************/
+  secret: 'ffbef9b6711dc3130e47e22d46fee23c',
+
+
+  /***************************************************************************
+  *                                                                          *
+  * Set the session cookie expire time The maxAge is set by milliseconds,    *
+  * the example below is for 24 hours                                        *
+  *                                                                          *
+  ***************************************************************************/
+
+  // cookie: {
+  //   maxAge: 24 * 60 * 60 * 1000
+  // },
+
+  /***************************************************************************
+  *                                                                          *
+  * Uncomment the following lines to set up a Redis session store that can   *
+  * be shared across multiple Sails.js servers.                              *
+  *                                                                          *
+  * Requires connect-redis (https://www.npmjs.com/package/connect-redis)     *
+  *                                                                          *
+  ***************************************************************************/
+
+  // adapter: 'redis',
+
+  /***************************************************************************
+  *                                                                          *
+  * The following values are optional, if no options are set a redis         *
+  * instance running on localhost is expected. Read more about options at:   *
+  *                                                                          *
+  * https://github.com/visionmedia/connect-redis                             *
+  *                                                                          *
+  ***************************************************************************/
+
+  // host: 'localhost',
+  // port: 6379,
+  // ttl: <redis session TTL in seconds>,
+  // db: 0,
+  // pass: <redis auth password>,
+  // prefix: 'sess:',
+
+
+  /***************************************************************************
+  *                                                                          *
+  * Uncomment the following lines to set up a MongoDB session store that can *
+  * be shared across multiple Sails.js servers.                              *
+  *                                                                          *
+  * Requires connect-mongo (https://www.npmjs.com/package/connect-mongo)     *
+  * Use version 0.8.2 with Node version <= 0.12                              *
+  * Use the latest version with Node >= 4.0                                  *
+  *                                                                          *
+  ***************************************************************************/
+
+  // adapter: 'mongo',
+  // url: 'mongodb://user:password@localhost:27017/dbname', // user, password and port optional
+
+  /***************************************************************************
+  *                                                                          *
+  * Optional Values:                                                         *
+  *                                                                          *
+  * See https://github.com/kcbanner/connect-mongo for more                   *
+  * information about connect-mongo options.                                 *
+  *                                                                          *
+  * See http://bit.ly/mongooptions for more information about options        *
+  * available in `mongoOptions`                                              *
+  *                                                                          *
+  ***************************************************************************/
+
+  // collection: 'sessions',
+  // stringify: true,
+  // mongoOptions: {
+  //   server: {
+  //     ssl: true
+  //   }
+  // }
+
+};

package/test/fixture/config/sockets.js

@@ -1,141 +1,141 @@
-/**
- * WebSocket Server Settings
- * (sails.config.sockets)
- *
- * These settings provide transparent access to the options for Sails'
- * encapsulated WebSocket server, as well as some additional Sails-specific
- * configuration layered on top.
- *
- * For more information on sockets configuration, including advanced config options, see:
- * http://sailsjs.org/#!/documentation/reference/sails.config/sails.config.sockets.html
- */
-
-module.exports.sockets = {
-
-
-  /***************************************************************************
-  *                                                                          *
-  * Node.js (and consequently Sails.js) apps scale horizontally. It's a      *
-  * powerful, efficient approach, but it involves a tiny bit of planning. At *
-  * scale, you'll want to be able to copy your app onto multiple Sails.js    *
-  * servers and throw them behind a load balancer.                           *
-  *                                                                          *
-  * One of the big challenges of scaling an application is that these sorts  *
-  * of clustered deployments cannot share memory, since they are on          *
-  * physically different machines. On top of that, there is no guarantee     *
-  * that a user will "stick" with the same server between requests (whether  *
-  * HTTP or sockets), since the load balancer will route each request to the *
-  * Sails server with the most available resources. However that means that  *
-  * all room/pubsub/socket processing and shared memory has to be offloaded  *
-  * to a shared, remote messaging queue (usually Redis)                      *
-  *                                                                          *
-  * Luckily, Socket.io (and consequently Sails.js) apps support Redis for    *
-  * sockets by default. To enable a remote redis pubsub server, uncomment    *
-  * the config below.                                                        *
-  *                                                                          *
-  * Worth mentioning is that, if `adapter` config is `redis`, but host/port  *
-  * is left unset, Sails will try to connect to redis running on localhost   *
-  * via port 6379                                                            *
-  *                                                                          *
-  ***************************************************************************/
-  // adapter: 'memory',
-
-  //
-  // -OR-
-  //
-
-  // adapter: 'socket.io-redis',
-  // host: '127.0.0.1',
-  // port: 6379,
-  // db: 0,
-  // pass: '<redis auth password>',
-
-
-
- /***************************************************************************
-  *                                                                          *
-  * Whether to expose a 'get /__getcookie' route with CORS support that sets *
-  * a cookie (this is used by the sails.io.js socket client to get access to *
-  * a 3rd party cookie and to enable sessions).                              *
-  *                                                                          *
-  * Warning: Currently in this scenario, CORS settings apply to interpreted  *
-  * requests sent via a socket.io connection that used this cookie to        *
-  * connect, even for non-browser clients! (e.g. iOS apps, toasters, node.js *
-  * unit tests)                                                              *
-  *                                                                          *
-  ***************************************************************************/
-
-  // grant3rdPartyCookie: true,
-
-
-
-  /***************************************************************************
-  *                                                                          *
-  * `beforeConnect`                                                          *
-  *                                                                          *
-  * This custom beforeConnect function will be run each time BEFORE a new    *
-  * socket is allowed to connect, when the initial socket.io handshake is    *
-  * performed with the server.                                               *
-  *                                                                          *
-  * By default, when a socket tries to connect, Sails allows it, every time. *
-  * (much in the same way any HTTP request is allowed to reach your routes.  *
-  * If no valid cookie was sent, a temporary session will be created for the *
-  * connecting socket.                                                       *
-  *                                                                          *
-  * If the cookie sent as part of the connection request doesn't match any   *
-  * known user session, a new user session is created for it.                *
-  *                                                                          *
-  * In most cases, the user would already have a cookie since they loaded    *
-  * the socket.io client and the initial HTML page you're building.         *
-  *                                                                          *
-  * However, in the case of cross-domain requests, it is possible to receive *
-  * a connection upgrade request WITHOUT A COOKIE (for certain transports)   *
-  * In this case, there is no way to keep track of the requesting user       *
-  * between requests, since there is no identifying information to link      *
-  * him/her with a session. The sails.io.js client solves this by connecting *
-  * to a CORS/jsonp endpoint first to get a 3rd party cookie(fortunately this*
-  * works, even in Safari), then opening the connection.                     *
-  *                                                                          *
-  * You can also pass along a ?cookie query parameter to the upgrade url,    *
-  * which Sails will use in the absence of a proper cookie e.g. (when        *
-  * connecting from the client):                                             *
-  * io.sails.connect('http://localhost:1337?cookie=smokeybear')              *
-  *                                                                          *
-  * Finally note that the user's cookie is NOT (and will never be) accessible*
-  * from client-side javascript. Using HTTP-only cookies is crucial for your *
-  * app's security.                                                          *
-  *                                                                          *
-  ***************************************************************************/
-  // beforeConnect: function(handshake, cb) {
-  //   // `true` allows the connection
-  //   return cb(null, true);
-  //
-  //   // (`false` would reject the connection)
-  // },
-
-
-  /***************************************************************************
-  *                                                                          *
-  * `afterDisconnect`                                                        *
-  *                                                                          *
-  * This custom afterDisconnect function will be run each time a socket      *
-  * disconnects                                                              *
-  *                                                                          *
-  ***************************************************************************/
-  // afterDisconnect: function(session, socket, cb) {
-  //   // By default: do nothing.
-  //   return cb();
-  // },
-
-  /***************************************************************************
-  *                                                                          *
-  * `transports`                                                             *
-  *                                                                          *
-  * A array of allowed transport methods which the clients will try to use.  *
-  * On server environments that don't support sticky sessions, the "polling" *
-  * transport should be disabled.                                            *
-  *                                                                          *
-  ***************************************************************************/
-  // transports: ["polling", "websocket"]
-
-};
+/**
+ * WebSocket Server Settings
+ * (sails.config.sockets)
+ *
+ * These settings provide transparent access to the options for Sails'
+ * encapsulated WebSocket server, as well as some additional Sails-specific
+ * configuration layered on top.
+ *
+ * For more information on sockets configuration, including advanced config options, see:
+ * http://sailsjs.org/#!/documentation/reference/sails.config/sails.config.sockets.html
+ */
+
+module.exports.sockets = {
+
+
+  /***************************************************************************
+  *                                                                          *
+  * Node.js (and consequently Sails.js) apps scale horizontally. It's a      *
+  * powerful, efficient approach, but it involves a tiny bit of planning. At *
+  * scale, you'll want to be able to copy your app onto multiple Sails.js    *
+  * servers and throw them behind a load balancer.                           *
+  *                                                                          *
+  * One of the big challenges of scaling an application is that these sorts  *
+  * of clustered deployments cannot share memory, since they are on          *
+  * physically different machines. On top of that, there is no guarantee     *
+  * that a user will "stick" with the same server between requests (whether  *
+  * HTTP or sockets), since the load balancer will route each request to the *
+  * Sails server with the most available resources. However that means that  *
+  * all room/pubsub/socket processing and shared memory has to be offloaded  *
+  * to a shared, remote messaging queue (usually Redis)                      *
+  *                                                                          *
+  * Luckily, Socket.io (and consequently Sails.js) apps support Redis for    *
+  * sockets by default. To enable a remote redis pubsub server, uncomment    *
+  * the config below.                                                        *
+  *                                                                          *
+  * Worth mentioning is that, if `adapter` config is `redis`, but host/port  *
+  * is left unset, Sails will try to connect to redis running on localhost   *
+  * via port 6379                                                            *
+  *                                                                          *
+  ***************************************************************************/
+  // adapter: 'memory',
+
+  //
+  // -OR-
+  //
+
+  // adapter: 'socket.io-redis',
+  // host: '127.0.0.1',
+  // port: 6379,
+  // db: 0,
+  // pass: '<redis auth password>',
+
+
+
+ /***************************************************************************
+  *                                                                          *
+  * Whether to expose a 'get /__getcookie' route with CORS support that sets *
+  * a cookie (this is used by the sails.io.js socket client to get access to *
+  * a 3rd party cookie and to enable sessions).                              *
+  *                                                                          *
+  * Warning: Currently in this scenario, CORS settings apply to interpreted  *
+  * requests sent via a socket.io connection that used this cookie to        *
+  * connect, even for non-browser clients! (e.g. iOS apps, toasters, node.js *
+  * unit tests)                                                              *
+  *                                                                          *
+  ***************************************************************************/
+
+  // grant3rdPartyCookie: true,
+
+
+
+  /***************************************************************************
+  *                                                                          *
+  * `beforeConnect`                                                          *
+  *                                                                          *
+  * This custom beforeConnect function will be run each time BEFORE a new    *
+  * socket is allowed to connect, when the initial socket.io handshake is    *
+  * performed with the server.                                               *
+  *                                                                          *
+  * By default, when a socket tries to connect, Sails allows it, every time. *
+  * (much in the same way any HTTP request is allowed to reach your routes.  *
+  * If no valid cookie was sent, a temporary session will be created for the *
+  * connecting socket.                                                       *
+  *                                                                          *
+  * If the cookie sent as part of the connection request doesn't match any   *
+  * known user session, a new user session is created for it.                *
+  *                                                                          *
+  * In most cases, the user would already have a cookie since they loaded    *
+  * the socket.io client and the initial HTML page you're building.         *
+  *                                                                          *
+  * However, in the case of cross-domain requests, it is possible to receive *
+  * a connection upgrade request WITHOUT A COOKIE (for certain transports)   *
+  * In this case, there is no way to keep track of the requesting user       *
+  * between requests, since there is no identifying information to link      *
+  * him/her with a session. The sails.io.js client solves this by connecting *
+  * to a CORS/jsonp endpoint first to get a 3rd party cookie(fortunately this*
+  * works, even in Safari), then opening the connection.                     *
+  *                                                                          *
+  * You can also pass along a ?cookie query parameter to the upgrade url,    *
+  * which Sails will use in the absence of a proper cookie e.g. (when        *
+  * connecting from the client):                                             *
+  * io.sails.connect('http://localhost:1337?cookie=smokeybear')              *
+  *                                                                          *
+  * Finally note that the user's cookie is NOT (and will never be) accessible*
+  * from client-side javascript. Using HTTP-only cookies is crucial for your *
+  * app's security.                                                          *
+  *                                                                          *
+  ***************************************************************************/
+  // beforeConnect: function(handshake, cb) {
+  //   // `true` allows the connection
+  //   return cb(null, true);
+  //
+  //   // (`false` would reject the connection)
+  // },
+
+
+  /***************************************************************************
+  *                                                                          *
+  * `afterDisconnect`                                                        *
+  *                                                                          *
+  * This custom afterDisconnect function will be run each time a socket      *
+  * disconnects                                                              *
+  *                                                                          *
+  ***************************************************************************/
+  // afterDisconnect: function(session, socket, cb) {
+  //   // By default: do nothing.
+  //   return cb();
+  // },
+
+  /***************************************************************************
+  *                                                                          *
+  * `transports`                                                             *
+  *                                                                          *
+  * A array of allowed transport methods which the clients will try to use.  *
+  * On server environments that don't support sticky sessions, the "polling" *
+  * transport should be disabled.                                            *
+  *                                                                          *
+  ***************************************************************************/
+  // transports: ["polling", "websocket"]
+
+};