00:04:35  * ShekharReddyquit (Quit: Connection closed for inactivity)
03:30:07  * nimomojoined
03:34:24  * nimomoquit (Ping timeout: 248 seconds)
06:49:08  * omejoined
07:44:54  * ShekharReddyjoined
08:49:46  * omequit (Quit: Connection closed for inactivity)
09:12:41  * omejoined
11:45:10  * nimomojoined
11:49:46  * omequit (Quit: Connection closed for inactivity)
12:38:51  * nimomoquit (Remote host closed the connection)
14:48:41  * nimomojoined
14:53:09  * nimomoquit (Ping timeout: 264 seconds)
15:01:54  * nimomojoined
17:03:37  * hillctjoined
17:10:20  <hillct>Good afternoon all. I wonder if you could provide some guidance as to how to construct an express middleware objectoffering chainable methods that can be called, for example app.route.get(‘/profile’,havePerm().updateAny(‘profile’), profileController.admin); When I attempt to setup middleware that’s anything other than a single, simple function, I get all sorts of strict mode problems. What’s the correct struture for such a middleware that facilit
17:10:21  <hillct>the above calling convention?
17:13:06  * nimomoquit (Ping timeout: 252 seconds)
17:45:48  * nimomojoined
18:06:05  * nimomoquit (Ping timeout: 240 seconds)
18:07:23  * nimomojoined
18:16:02  * nimomoquit (Remote host closed the connection)
18:42:17  * nimomojoined
18:47:26  * nimomoquit (Ping timeout: 276 seconds)
20:04:01  * nimomojoined
22:03:12  * nimomoquit (Read error: Connection reset by peer)
22:03:27  * nimomojoined
23:05:07  * omejoined
23:09:24  * nimomoquit (Ping timeout: 260 seconds)
23:50:46  * nimomojoined