These are chat archives for canjs/canjs

25th
Nov 2015
Mihai Fantana
@fantanamihai
Nov 25 2015 08:15
@justinbmeyer thanks for the invite. unfortunately i couldn't attend
Jeroen Cornelissen
@jeroencornelissen
Nov 25 2015 08:26
@dylanrtt thx!
Problem was inside 2 other models where a convert happened for the myModels. When I did an extend in each model the problem was fixed.
Mihai Fantana
@fantanamihai
Nov 25 2015 09:08

guys i have question regarding use of define on objects that have as attributes other objects. e.g.

object: {
   attribute1: {
       array1: []
   }
}

Is there a way to use in object's Model a define on array1 attribute?
I would love to see a definition in the style of:

define: {
   'attribute1.array1': { ... }

but any other way will do

let me know if you'd like to be "in" the meeting .. I'll send you another link
Julian
@pYr0x
Nov 25 2015 16:59
can attend but cant talk, i am still at the office
Julian
@pYr0x
Nov 25 2015 17:28
pyr0x
ok
Julian
@pYr0x
Nov 25 2015 17:34
justin would you talk about can connect
cache lifetime?
for me
?
ok :)
Julian
@pYr0x
Nov 25 2015 17:39
i will send your
Paul Tichonczuk
@tracer99
Nov 25 2015 19:14
We're trying out the latest can (2.3.2) in our project, and we're getting this error on the initialization of some of our controllers.
"Uncaught TypeError: computedAttr.compute is not a function" in map.js on line 365, and if you press it again, its a new error
"Uncaught TypeError: value is not a function" in control.js on line 275
Previously running 2.6.2 where the map function for getting values from ATTR was much simpler.
Paul Tichonczuk
@tracer99
Nov 25 2015 19:20
The controller object has a constructor, and this seems to confuse the computedAttr function.