00:10:32  * jlloydquit (Quit: jlloyd)
00:13:48  * jlloydjoined
00:36:12  * jlloydquit (Quit: jlloyd)
01:06:16  * rfengquit (Quit: rfeng)
01:12:35  * rmgquit (Remote host closed the connection)
02:13:08  * rmgjoined
02:17:42  * rmgquit (Ping timeout: 250 seconds)
03:15:31  * rfengjoined
04:05:53  * rmgjoined
04:10:53  * rmgquit (Ping timeout: 272 seconds)
06:08:06  * rfengquit (Quit: rfeng)
06:45:23  * bajtosjoined
06:59:28  * Pelorusquit (Read error: Connection reset by peer)
07:06:03  * fabienfjoined
08:33:47  * bajtosquit (Quit: bajtos)
08:34:40  * bajtosjoined
10:12:55  * rmgjoined
10:17:04  * rmgquit (Ping timeout: 244 seconds)
10:31:33  * bajtosquit (Quit: bajtos)
10:56:22  * bajtosjoined
11:01:10  * bajtosquit (Ping timeout: 264 seconds)
11:27:22  * bajtosjoined
11:31:56  * bajtosquit (Ping timeout: 260 seconds)
12:28:09  * bajtosjoined
12:33:07  * bajtosquit (Ping timeout: 272 seconds)
13:26:19  * bajtosjoined
14:33:55  * bajtosquit (Quit: bajtos)
14:52:59  * rfengjoined
15:55:13  * bajtosjoined
15:55:17  * bajtosquit (Client Quit)
16:10:03  * rmgjoined
16:17:18  * bajtosjoined
16:17:40  <offline>bajtos: ping
16:55:35  * fabienf_joined
16:56:15  * fabienfquit (Read error: Connection reset by peer)
16:56:15  * fabienf_changed nick to fabienf
17:19:12  <rfeng>@fabienf I cannot respond to your private message. It says you are offline
17:19:36  <fabienf>rfeng: that's weird
17:19:40  <fabienf>just a sec
17:19:55  <rfeng>Let’s chat here
17:19:57  <bajtos>offline: pong
17:20:03  <fabienf>sure
17:20:29  <rfeng>I feel the heats :-)
17:20:37  <rfeng>I guess there are two options
17:20:42  <fabienf>;)
17:21:16  <rfeng>1. Bring back the 1.x solution - always have the built-in models subclassed in model jsons
17:21:51  <rfeng>2. Introduce a way to reference existing models (maybe from code) and provide a way to customize it in model json
17:22:19  <rfeng>Do you want to summarize what issues we have so far?
17:22:21  <fabienf>can we have both? ;-) 1 seems like a reasonable default, and 2 sounds great to have
17:22:38  <rfeng>I agree
17:22:42  <fabienf>2 from code only btw
17:22:49  <rfeng>y
17:23:17  <rfeng>We also need to make it clear what model json and model-config.json can do
17:23:24  <fabienf>how hard would it be to bring 1. back?
17:23:45  <rfeng>1 is simple, just fix the scaffolding generator template
17:24:15  <rfeng>This will also allow the built-in models to be used as relations/acls etc
17:24:15  <fabienf>yes, I was talking with bajtos this morning, and there's even some confusion regarding the actual split of concerns introduced by /common/ /client/ and /server/
17:24:33  <rfeng>yes
17:24:46  <rfeng>It becomes complicated
17:24:56  <rfeng>two many dimensions
17:25:00  <rfeng>too
17:25:42  <fabienf>yeah, so according to bajtos, it's not really certain that user.js in /common refers to the same model as user.js on /server or /client
17:25:55  <fabienf>o_O
17:25:58  <rfeng>I think there is a proposal to prompt for slc loopback:model to decide if server/common should be used
17:26:32  <rfeng>I’m fine to only generate subclasses of built-in models in server
17:27:09  <bajtos>that does not make sense in isomorphic/full-stack app
17:27:11  <rfeng>but then the relation stuff may be lose visibility
17:27:41  <bajtos>it does not makes sense for models shared between the client and the server, e.g. Customer extends User
17:28:00  <bajtos>for server-only models like Role or RoleMapping, generating subclasses in server/ is ok
17:28:01  <rfeng>@bajtos What’s the visibility scope between common and server?
17:28:22  <rfeng>server only models can reference common but not vice versa, right?
17:28:30  <fabienf>sec, I'll catch the conversation in a bit (on the phone)
17:28:39  <bajtos>loopback-boot resolves models mentioned in `model-config.json` from both `common/models` and `server/models`
17:28:52  <bajtos>rfeng: yes, as you wrote
17:28:59  <rfeng>ok
17:30:35  <rfeng>It has to be extra cafeful to really make a model common
17:30:59  <rfeng>For example, when a model is extended with custom methods, it may break the compatibility
17:31:46  <rfeng>We’ll have to run for a meeting now
17:32:34  <fabienf>rfeng, OK catch you later
17:39:24  * rmgquit (Remote host closed the connection)
18:18:35  * rmgjoined
18:33:00  * octetcloudjoined
18:33:52  <rfeng>@fabienf I rememeber you have a doc to show how to define embedsMany in LDL?
18:34:08  <fabienf>rfeng, yes a gist?
18:34:23  <rfeng>Can you give me the link?
18:34:32  <fabienf>https://gist.github.com/fabien/ccce7f1de399c0227ce6
18:35:01  <rfeng>thanks
18:35:07  <fabienf>you're welcome
18:35:45  * bajtosquit (Quit: bajtos)
19:04:13  * bajtosjoined
19:06:03  * bajtosquit (Client Quit)
19:18:24  <fabienf>rfeng: ping
19:28:47  * rfengquit (Quit: rfeng)
20:08:06  * rfengjoined
20:29:44  * fabienfquit (Quit: fabienf)
21:53:52  * Pelorusjoined
23:52:24  * octetcloudquit (Ping timeout: 250 seconds)