You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is related to #25
Even after the updates for #25 we will have to update the attribute on the view.domNode.attr in order to update the value in handlebars. It would be better if we could update the view.attr instead, but that would require some data binding between the view and view.domNode attrs.
The text was updated successfully, but these errors were encountered:
In order to solve the problem of the binding not being "live" I guess a solution would be for the ViewBase Widget to be the widget that received the template. Instead of being 2 different widgets?
The problem is that we need a different Widget for each view (because of the template issue requiring us to register a different one each time) but this should be doable? For example in the Load controller instead of directly instantiating the View we would:
This issue is related to #25
Even after the updates for #25 we will have to update the attribute on the view.domNode.attr in order to update the value in handlebars. It would be better if we could update the view.attr instead, but that would require some data binding between the view and view.domNode attrs.
The text was updated successfully, but these errors were encountered: