Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Christopher Oliphant
@RALifeCoach
the line throwing the exception is oldChild._nestedReference.each(_nestedReference is null
oldChild is not a type Constructor, but an Object
Kevin Phillips
@phillipskevin
ok
Christopher Oliphant
@RALifeCoach
@phillipskevin do you have an estimate as to when you can have a look?
Kevin Phillips
@phillipskevin
I am traveling at a client this week so not really.
I’m going to look at the issue today, but don’t have any idea if I’ll know how to fix it.
Julian
@pYr0x
@RALifeCoach can you reproduce this issue with lazymap on a simple and short example
Christopher Oliphant
@RALifeCoach
I knew someone was going to ask that. Yes I can.
Julian
@pYr0x
;) we have to make tests for CI
so a test that reproduce this problem is the first step to fix this
btw. can-map-lazy is currently for canjs 3.0
not for 2.x
Kevin Phillips
@phillipskevin
thanks, I was trying to figure that out
Christopher Oliphant
@RALifeCoach
I know it’s scheduled for 3.0, but gave me the best performance improvement so far
Kevin Phillips
@phillipskevin
require(‘can/map/lazy'); without installing can-map-lazy
there is a can.LazyMap plugin for 2.x also
right @pYr0x ?
Julian
@pYr0x
lazymap is currently (in canjs 2.x) integrated.
https://github.com/canjs/canjs/tree/master/map/lazy
@RALifeCoach you can look into this https://github.com/canjs/canjs/blob/master/map/lazy/nested_reference_test.js
if i understand right, you have problems with nested properties?
Kevin Phillips
@phillipskevin
but it’s not pulled in here: https://github.com/canjs/canjs/blob/master/map/map.js#L16
Christopher Oliphant
@RALifeCoach
Here is the JSBin http://jsbin.com/qahepi/edit?html,js,console,output
yes - nested properties are causing the problem
Julian
@pYr0x
@phillipskevin yep, lazymap extends can.map
@RALifeCoach this stache isnt very short
and the test also
Christopher Oliphant
@RALifeCoach
Sorry - I can pare it down
Julian
@pYr0x
why?
this code isnt a testable code...
Christopher Oliphant
@RALifeCoach
it is much shorter now
Julian
@pYr0x
so we need the component?
can you remove that
Christopher Oliphant
@RALifeCoach
Better?
Julian
@pYr0x
didnt see any changes?
still a component
Christopher Oliphant
@RALifeCoach
http://jsbin.com/qahepi/14/edit?html,js,console,output
yes there is still a component
how’s how my code works
Julian
@pYr0x
can you remove that too
Christopher Oliphant
@RALifeCoach
When I removed the component it stopped crashing
Julian
@pYr0x
;)
good to know
so the problem is not lazymap
it is the component?
Christopher Oliphant
@RALifeCoach
http://jsbin.com/qahepi/15/edit?html,js,console,output
the line of code that is throwing the exception is in lazy map
Julian
@pYr0x
yes.. but the problem can come from other code
Kevin Phillips
@phillipskevin
the component probably causes lazyMap to set up the binding
the component binds, and lazymap tries to initialize the data