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
Each binding has a unique name, such as value and text. Bindings generally take a single parameter; for example: text: 'Hello'.
Some binding (options, foreach, template) often take multiple parameters. Currently there are two methods used to specify multiple parameters. 'options' uses multiple top-level bindings (options: list, optionsText: 'name', optionsValue: 'id'), but only 'options' has a binding handler. 'foreach' and 'template' use a sub-object (template: {name: 'me', data: mydata}), but can also be called with a single parameter (template: 'me').
Another class of bindings (css, style, attr, event) also take multiple parameters, but for a different reason. These current accept an object where the property name is the class, style, etc. to be bound to and the value is the dependency for that binding.
I propose that all independent bindings be specified at the top level. If a binding requires multiple parameters, these will specified using a sub object. In the case of bindings that require two parameters (key and value), we'll use a method of combining the binding type with the key, such as style.color: 'blue'
The text was updated successfully, but these errors were encountered:
…ew $parentContext variable
Benefit #1: Can reach custom properties on *all* ancestor contexts, and are not limited to those that haven't been overwritten
(e.g., if we had $index, would now be able to reach all ancestor $index values, not just the closest one)
Benefit #2: Allows discrimination between properties at the current level and properties at the parent level, which
is good because not all custom properties may make sense to inherit.
Each binding has a unique name, such as value and text. Bindings generally take a single parameter; for example: text: 'Hello'.
Some binding (options, foreach, template) often take multiple parameters. Currently there are two methods used to specify multiple parameters. 'options' uses multiple top-level bindings (options: list, optionsText: 'name', optionsValue: 'id'), but only 'options' has a binding handler. 'foreach' and 'template' use a sub-object (template: {name: 'me', data: mydata}), but can also be called with a single parameter (template: 'me').
Another class of bindings (css, style, attr, event) also take multiple parameters, but for a different reason. These current accept an object where the property name is the class, style, etc. to be bound to and the value is the dependency for that binding.
I propose that all independent bindings be specified at the top level. If a binding requires multiple parameters, these will specified using a sub object. In the case of bindings that require two parameters (key and value), we'll use a method of combining the binding type with the key, such as style.color: 'blue'
The text was updated successfully, but these errors were encountered: