Can reference scope be used in conjunction w/ expressions? Previously I’ve done ($click)=“attr(‘foo’, ‘bar’)”, however I’m not sure how to do the equivalent with template reference variables
@Bajix Generally, yes. You can do
($click)=“attr('foo', *bar)” assuming *bar is in the ref scope
I’d like to do so on the template reference rather than the current scope context
Hmm, I don't think that's possible yet. You can call a method of
*foo though
I feel like it would’ve been maybe more useful to just do *.foo
Have
* be an empty map
That way you always access it’s methods
Here is a solution if you don't mind the extra verbosity http://jsbin.com/hagejaloxi/edit?html,js,output
or %scope.attr(‘*foo’, ‘bar’)
scope.attr() works in the method but for some reason I couldn't get it to work in the expression
I’ve noticed call expressions struggle w/ promises
You can’t do $(click)=“post.save().then(@redirect, @handleError)"
But I suppose ($click)”="post.save(@redirect, @handleError)” might work
I have another performance question. I have a large stache template that creates one row of a div table. There are 156 rows to the entire table. The entire table is loaded and then reloaded as the page is loaded. The load takes about 4 seconds which isn’t great, but I can live with. The reload varies as shown below.
this.attr('player', player);reloads in 1.5 seconds
if (this.attr('player')) {
this.attr('player').attr(player);
} else {
this.attr('player', player);
}reloads in 4 seconds. Yet I was told the this was the better way to go.
Good morning. If I have a virtual property using the define
get function, can I set it up in a way that it builds a new object the first time its accessed and subsequent times it only modifies the existing object, rather than creating a brand new object? I have a template that uses this object and i'd like it to not have to re-render the entire template each time the object's dependents change.
How do you build the new object? What do you do with the new object when it’s built?
The new object is a something like this and it is used to render a form:
this.attr('fields').forEach(function(fieldname){
newObj[fieldname] = {
alias: self.formatField(fieldname),
value: self.attr('formObject' + '.' + fieldname),
//other field properties
};
});
At the moment, I'm basically returning the newObj property, from the
get function
Use a switch:
if (!this.objectBuilt) { build; this.objectBuilt = true;}
I was trying to set it up like that, at the beginning of the get function, I would check to see if there was a lastSetValue.
get: function(lastValue){
if(lastValue){
//modify and return lastValue
} else { /* build new value */}
But lastValue is always undefined
using this.lastValue would work. So would
this.attr(‘this field name’, object);
place that after building the object
I should use
this.attr('fieldName', newValue); instead of returning the object?
Returning a value in a getter won’t set the value. That only works in a setter.
Okay, that makes sense. One more question, the getter should still return the object, correct?
return this.attr('thisFieldName') after setting the value
Returning the object makes it available to the code trying to use the object.
I am trying to execute a method in the view model, via the component
I can get the viewModel using
$el.viewModel()
but I can’t execute
$el.viewModel().someMethod()
I can see and update properties via
$el.viewModel().xxx
can.grep() Why is it that I cannot find any documentation on this function?
@RALifeCoach what happens when you try to execute the method?
(I should have checked there first)
Now I have to figure out why it’s not working in my unit test