02:51:28  * rmgquit (Remote host closed the connection)
03:48:16  * rmgjoined
03:52:58  * rmgquit (Ping timeout: 240 seconds)
04:02:31  * rmgjoined
04:29:09  * rmgquit (Remote host closed the connection)
04:39:36  * rmgjoined
05:13:08  * bajtosjoined
06:31:34  * rmgquit (Remote host closed the connection)
07:06:17  * bajtosquit (Quit: bajtos)
07:21:30  * bajtosjoined
10:08:42  * bajtosquit (Quit: bajtos)
10:43:20  * bajtosjoined
14:26:53  * Gogejoined
14:27:04  <Goge>good day :)
14:27:24  <bajtos>hello :)
14:28:41  <Goge>Is there any multi-language localization implementation for the models in LoopBack? Is there a convention?
14:30:42  <Goge>I thought of adding a method to the model constructor and using nested documents {"d" : { "en" : "en", "fr" : "fr" } }
14:31:07  <Goge>however I am unsure is LoopBack supports nested document storage.
14:31:18  <bajtos>what would you like to localize?
14:31:19  <bajtos>https://github.com/strongloop/loopback/issues/255
14:32:00  <bajtos>I believe nested documents are supported, they are stored as JSON or varchar column in SQL databases
14:33:11  <Goge>thanks. I'm backing the datastore with mongodb and would liked to use native document store.
14:35:31  <Goge>The hope was to have the localization stored in the db and accessible by the rest endpoints. LoopBack is being used to create a content delivery network, no client facing pages would be served by the LoopBack instance.
14:47:24  * rhalffjoined
14:49:23  <Goge>how can nested documents be defined in a model?
14:55:18  <bajtos>Use data-type object
14:55:51  <bajtos>http://docs.strongloop.com/display/DOC/LDL+data+types
14:59:29  <Goge>thanks!
15:18:43  * rmgjoined
15:31:04  * bajtosquit (Quit: bajtos)
16:16:18  * Gogequit (Ping timeout: 240 seconds)