Open OneGeek opened 9 years ago
I'm having the same issue. Have you found a solution?
I do not believe I managed to make this happen.
This works for me. Did you bind your computed correctly to an event e.g.
'input#my-computed': "value:myComputed, events:['input']"
Did you check that the attributes you return in the set
function belong to a model defined in bindingSources
(e.g. the model associated to the view)? Also ensure that in the set
of myComputed
you do not try to set this attribute directly (which would result in a recursive set
call).
I have a view with a computed property that defines a
set
function which returns an object with some properties set. I've bound this to an<input>
with the declarationvalue:myComputed
.The documentation of computeds describes that the return value of a computed's
set
is merged into the model when called.I've confirmed the following
<input>
view.model.set('myComputed', '...')
also updates the<input>
set
does get called when I modify the<input>
What I expect to work, but doesn't
<input>
does not update the modelview.setBinding('myComputed', '...')
does not update the modelLooking at the source code I see the value I return from
set
gets as far as being returned from a call toaccessor(self.get(self.$el, readAccessor(accessor), evt))
in the definition of EpoxyBinding, but nothing is done with it at that point.My question
Am I misunderstanding the documentation here or is this a bug?