Can't set any isolate scope properties

[azevedo]

The latest commit makes it impossible to set any isolate scope properties, as it is not extendable anymore.

[menems]

#8 related

You replace the name as controllerAs by '$ctrl', why ?
so now we have to explicitly add controllerAs ...

[benoror]

angular/angular.js#13710 cc @azevedo-252 @menems

[azevedo]

@menems I understand that, and the issue is not about that feature in particular.
What I mean is that we can no longer set isolate scope properties with the bindings property, like so

angular
.module('app', [])
.component('counter', {
  bindings: {
    count: '='
  },
  ...
});

because it no longer maps it to the real scope property of the DDO. What you get in the end is something like:

angular
.module('app', [])
.directive('counter', {
  scope: {}, // notice `count` is missing
  ...
});

This is the change that causes this. It doesn't assign options.bindings anywhere.

[toddmotto]

@azevedo-252 You okay to test last commit on master? :)

[toddmotto]

Latest changes should mirror the new 1.5 syntax:

scope: options.bindings || {},
bindToController: !!options.bindings,

Set scope: { foo: '=' } or scope: {} and bindToController: [Boolean]. That way it works on 1.3 still.

[toddmotto]

@benoror If the last commit fixes, then 0.0.3 is good to go on npm

[azevedo]

@toddmotto it's working
👍

[toddmotto]

@azevedo-252 Awesome, thanks! :)

[benoror]

npm publish'ed 👍