00:07:32  * rfengquit (Quit: rfeng)
00:13:43  * octetcloudquit (Ping timeout: 272 seconds)
00:17:49  * circ-user-pHtq3joined
00:22:04  * Pelorusjoined
00:22:10  * circ-user-pHtq3quit (Ping timeout: 255 seconds)
01:01:29  * Pelorusquit (Quit: Pelorus)
01:13:08  * Pelorusjoined
03:11:40  * rmgjoined
03:49:31  * rmgquit (Remote host closed the connection)
03:59:53  * rmgjoined
04:12:27  * rmgquit (Remote host closed the connection)
04:12:57  * rmgjoined
04:18:00  * rmgquit (Ping timeout: 272 seconds)
04:26:25  * rfengjoined
04:34:29  * Pelorusquit (Quit: Pelorus)
04:42:14  * Pelorusjoined
05:02:14  <Pelorus>rfeng: on the loopback.io page it refers to ‘slc looback’. This should be ‘yo loopback’ now right?
05:03:01  <rfeng>See http://strongloop.com/strongblog/update-to-installer/
05:11:20  <Pelorus>rfeng: OK, thanks. Is there a way to get additional debugging out of loopback? Just trying to work out how the routing works togther with the relations
05:11:37  <rfeng>yes
05:12:07  <rfeng>http://docs.strongloop.com/display/LB/Debugging+LoopBack+apps
05:15:04  <Pelorus>great. And for debugging mulitple files at once or global debug?
06:02:28  <rfeng>see https://github.com/visionmedia/debug#conventions
06:03:05  <Pelorus>can anyone shed some light on how these routes are processed? > /api/customers?filter[include][reviews]=author < I’ve been trying to track it down using debugging, but had little sucess.
06:03:48  <rfeng>it’s handled by strong-remoting
06:04:11  <rfeng>DEBUG=strong-remoting:* will do
06:04:31  <Pelorus>rfeng: regarding debug#conventions - awesome. thanks
06:04:33  <rfeng>what do you try to figure out?
06:05:56  <Pelorus>It’s just that I’ve not seen [] in a URL before & trying to understand how it is processed. I’d trying get data via explorer, as it is in the web page, but not working for me.
06:22:41  <rfeng>oh, that’s the qs module
06:23:10  <rfeng>https://github.com/hapijs/qs
06:23:38  <rfeng>you can use stringified json too as the filter param
06:23:44  <rfeng>sometimes it’s less confusing
06:27:05  <Pelorus>Ah-ha. very good.
06:27:43  <Pelorus>I was reading it all wrong.
06:41:10  * fabienfjoined
06:43:09  * Pelorusquit (Quit: Pelorus)
06:46:19  * rmgjoined
06:54:22  * rmgquit (Read error: Connection reset by peer)
06:54:39  * rmgjoined
07:23:05  * rmgquit (Remote host closed the connection)
08:53:34  * rfengquit (Quit: rfeng)
09:35:57  * Pelorusjoined
09:50:48  * Pelorusquit (Quit: Pelorus)
10:07:17  * Pelorusjoined
10:25:14  * Pelorusquit (Quit: Pelorus)
11:22:47  * Pelorusjoined
11:38:24  * Pelorusquit (Quit: Pelorus)
11:44:26  * Pelorusjoined
12:30:54  * Pelorusquit (Quit: Pelorus)
12:42:04  * Pelorusjoined
12:43:36  * Pelorusquit (Client Quit)
13:54:55  * circ-user-pHtq3joined
13:59:22  * circ-user-pHtq3quit (Ping timeout: 255 seconds)
14:06:34  * circ-user-pHtq3joined
14:22:14  * octetcloudjoined
14:38:04  * rfengjoined
14:49:37  * octetcloudquit (Ping timeout: 272 seconds)
15:08:27  * fabienfquit (Quit: fabienf)
15:16:19  * circ-user-pHtq3quit (Ping timeout: 255 seconds)
15:16:42  * octetcloudjoined
16:10:24  * rmgjoined
16:40:33  * octetcloudquit (Quit: WeeChat 0.4.2)
19:04:28  * Pelorusjoined
19:11:04  * Pelorusquit (Quit: Pelorus)
19:12:56  * Pelorusjoined
19:35:53  <Pelorus>Newb question - in the datagraph example, what are lines 9 to 29 actually acheiving? https://github.com/strongloop/loopback-example-datagraph/blob/master/models/datagraph.js
20:04:32  <Pelorus>Just seems to dump data to terminal if in debug mode.
20:56:46  * Pelorusquit (Quit: Pelorus)
21:02:41  * Pelorusjoined
21:02:41  * Pelorusquit (Client Quit)
21:03:26  * Pelorusjoined
21:13:04  * Pelorusquit (Quit: Pelorus)
21:13:33  * Pelorusjoined
21:24:33  * Pelorusquit (Quit: Pelorus)