it seems the promise's call to attr('state', state)sets up a dependency if i'm not mistaken, anyway.
if you could fix the jsbin to work without binding a noop handler to work correctly i.e.
- update the
statewhenpromisechanges and when resolved/rejected - update the
promiseifidKeychanges - update the
modelwhenpromiseresolves
that would grant me a good night sleep!
@espretto The binding on set seems to be a 2.0.3 bug. If you reference latest, your approach works fine: http://jsbin.com/xahaxugobi/1/edit?html,js,console,output
2.0.3 was what i found in jsbin's list, my bad. the binding on set persists in latest though see here. your solution does work for me, however intercepting the
idKey setter kind of defeats the purpose of observables, after all, idKey shouldn't have to know what depends on it at all. i'll call it a day. again thanks for your time and efforts! hope to see you around here soon.
@espretto Sorry, I must’ve linked you incorrectly. This is your original code running on latest. It works as I think you’d expect: http://jsbin.com/kimuzenele/3/edit?html,js,console,output
Now, as for this new example. Let me look into it.
in handlebars I would do this -- tabindex='{{@index}}'
getting NaN with stache
dimensionList --> Array
is it even documented anywhere? http://canjs.com/docs/can.stache.html
I am fiddling with it now and it seems that sometimes I do also get NaN
@opolyo01 I can get it to work with the
{{#each}}helper: http://jsbin.com/warebexisa/edit?html,js,output
@BigAB the can.view.attr page shows making a
http://canjs.com/docs/can.view.attr.html#section_Readingvaluesfromthescope_
fade-in-when="{prop}" attribute. you could probably apply the same principle to other animationshttp://canjs.com/docs/can.view.attr.html#section_Readingvaluesfromthescope_
or i am too late
why?
gratulation ;)
Anyone know the best way to solve this in CanJS? I have multiple components that all need the same function - isLoggedIn() for example. Right now I've needed to copy that function into every component which feels very wrong. My gut reaction was to put that in my main component assuming it acts as a parent to all other components and assuming child components inherit from the parent. But I'm pretty sure those assumptions are not correct. Any tips on how to correctly do this is much appreciated!
a better way, which also works without leaking scope, would be to pass it to the child components
there may also be value in simply extracting the function to an outside service if possible and including it in all of your components that need it
@dylanrtt - Thanks! We haven't set
leakScope: false anywhere so let me double check and see why the child was not inheriting from the parent scope. I did just notice that my isLoggedIn was set as a variable on the parent scope and not as a function - maybe that's it? I'll find out. At least knowing that child components should inherit their parent scopes is all I need - I'm sure I'm doing something else wrong then. Thanks again!
I'll try to create a fiddle
I'll try to dig deeper in that and see if there's a way to make it work as expected with can-value's in there..
i doubt that's related to the bug though
@whitecolor You can try this helper to opt out of live binding for a property: https://gist.github.com/marshallswain/7e07a23971ab70f78a11