Christopher Dieringer
Christopher Dieringer
@bryanspears, looks like you had an open PR for this issue. what was the scoop w/ that?
Ah, difficult to believe this hasn't come up before. I thought we handled this case? Checkout _setRender. When you extend the view, we wrap it, call your new render, and...
this affects &-view, but at the end-of-the-day, the solution is really begging for extra work on &-collection-view to host an eventing Collection. I don't however, see the potential perf gains?...
for the time being, i'm experimenting with ``` js initialize: function(attrs) { for (var def in this._definition) { var defDfl = this._definition[def].default; if (this._definition[def].required && (!defDfl || (typeof defDfl ===...
yikes, can't believe i didn't find those oldies-but-goodies > And if they are undefined and there is a default? Should required and default be mutually exclusive? i would say they...
@pgilad i like it. i'm trying to poke holes in it for hardening sake, but im comin' up short!
I would love if someone (&-js community member perhaps?? :) ) had some time to hack a PR together for this. I think that the issue is acknowledged widely enough,...
agreed. > How would it deal with the fact that you'd still get model.drivingDistance === undefined until the callback was done a key question that would still require bottoming out...
i've had to design around this as well. it's definitely do-able. in my case, i've wanted to bind listeners to an element that :dash: (whoosh) disappears :dash: once I render...