Usage of bindable in local template is not consistent with existing bindable
See original GitHub issueExtracted from #1086
Our existing build time <bindable>
is using attribute name
and attribute
. This is inline with Aurelia 1.
But local template use attribute property
. This is probably overlooked, need to change to name
and attribute
.
<template as-custom-element="foo-bar">
<bindable property="prop"></bindable>
Level One ${prop}
</template>
<foo-bar prop.bind="prop"></foo-bar>
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
In WPF, why doesn't TemplateBinding work where Binding ...
The TemplateBinding transfers data from the templated parent to the property that is template bound. If you need to transfer data in the ......
Read more >Issue in using Binding with ElementName in Data Template ...
In UserView.xaml, x:Bind is working fine. but for binding the column visibility the value will not be available in UserModel. Hence used ......
Read more >x:Bind outside data templates is extremely inconsistent #2508
Describe the bug Apparently it is possible to use x:Bind to bind to a field in code behind outside a data template.
Read more >Data binding helper elements - Polymer Project
Polymer data binding is only available in templates that are managed by Polymer. So data binding works inside an element's local DOM template,...
Read more >The "template" binding - Knockout.js
Internally, those control flow bindings capture the HTML markup contained in your element, and use it as a template to render against an...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Sayan751 yes it’s still inconsistent. I think we should have it as
name
+attribute
I meant we could do it everywhere in 1 sweep later, to align 2 versions together, also to align local template & convention as well. The inconsistency probably should be resolved before alpha.