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
To do so currently requires application or third-party system to implement “binding source factory” API, which let you parse {{expression}} yourself and determine what to do with the expression (you can see some implementations in liaison/alternateBindingSource.js). May be worthwhile to consider doing that right in liaison. It may involve supporting “named scope” ({{name in model}}).
The text was updated successfully, but these errors were encountered:
Not sure to completely understand the topic as I never used liaison so ignore this remark if I am out of the scope of this issue.
Angular ng-repeat directive is working like that ("item in list") and creates a child scope. It allows to use other list properties or other properties of the scope inside the loop.
My 2 cents
As far as I see how Angular works on repeat, it appears to put parent scope to scope’s prototype. So scope has read-only access to parent scope’s properties. liaison (as well as Polymer) do not have “scope” notion and they work in a way of putting model to <template>. It would be intrusive to overwrite prototype of such model for the sake of access to parent <template>’s model properties.
To do so currently requires application or third-party system to implement “binding source factory” API, which let you parse
{{expression}}
yourself and determine what to do with the expression (you can see some implementations in liaison/alternateBindingSource.js). May be worthwhile to consider doing that right in liaison. It may involve supporting “named scope” ({{name in model}}
).The text was updated successfully, but these errors were encountered: