@bindable's defaultBindingMode property don't work.

[andrevlins]

If you specify a default binding mode in @bindable decorator It will not be used when you bind you attribute throught .bind.

<my-custom-element  my-attribute.bind="foo"></my-custom-element>

if my-attribute is defined as

@bindable({ name: 'myAttribute', attribute: 'my-attribute', defaultBindingMode: TWO_WAY})

foo will not be updated.... but if you use:

<my-custom-element  my-attribute.two-way="foo"></my-custom-element>

then foo will be updated as expected.

I'll make a repro on top of skeleton-nav later...

[jods4]

The syntax has changed, now it's defaultBindingMode: bindingMode.twoWay but it is still not working...

[andrevlins]

@jods4 you have to import import {bindingMode} from 'aurelia-framework';

[jods4]

I know and I did (I am using TypeScript so that would have been an error otherwise). Does it work for you now?

I have a customAttribute with bindable properties, like so:

export class SomethingCustomAttribute {
  @bindable({ defaultBindingMode: bindingMode.twoWay })
  public x: string = null;
}

But when I use it so: <input something='{ x.bind = yada }' /> yada does not update but when I use it like this: <input something='{ x.two-way = yada }' /> it does.

[EisenbergEffect]

Ok, I think this is a confusion about how to use custom attributes. A simple custom attribute that wants two-way binding to be the default should be declared like this:

@customAttribute('my-attr', bindingMode.twoWay)
export class MyAttr {
  valueChanged(newValue, oldValue) {
    //do stuff
  }
}

For simple attributes, you don't define the properties, the framework provides on automatically...and so the binding mode need to be declared on the class. You only declare it on properties if you have an attribute that maps to multiple properties (an options attr).

[jods4]

@EisenbergEffect I am not sure I understand fully.

As my example shows, I'm trying to have an options attribute. I only used x in the example, but of course I actually have a bunch of attributes.

Something more like this (just an example, mind you):
<input auto-complete='src.one-time: suggestions, selected.bind: value' />

In this case selected.bind would not be two-way, even tough the field in the custom attribute is declared with @bindable({ defaultBindingMode: bindingMode.twoWay }) selected;.

[EisenbergEffect]

Ok, I may have misunderstood. I'll re-open this and investigate further.