`ng-true-value` and `ng-false-value` take expressions vs. string values in AngularJS

[chalin]

Consider the following example taken from the AngularJS input[checkbox] page

<script>
  function Ctrl($scope) {
    $scope.value1 = true;
    $scope.value2 = 'YES'
  }
</script>
<form name="myForm" ng-controller="Ctrl">
  Value1: <input type="checkbox" ng-model="value1"> <br/>
  Value2: <input type="checkbox" ng-model="value2"
                 ng-true-value="YES" ng-false-value="NO"> <br/>
  <tt>value1 = {{value1}}</tt><br/>
  <tt>value2 = {{value2}}</tt><br/>
 </form>

This needs to be tweaked for it to work in AngularDart: namely, the arguments to ng-true-value and ng-false-value are taken as expressions. Is this intentional? If so, then to documentation will need to be updated.

[chalin]

If these directives are meant to behave like in Ajs, then the fix is simple too: annotate the directive attributes with @NgAttr. Just waiting for confirmation of the desired behavior.

[caitp]

Using expressions here is probably preferable (it's been asked for in Ajs a fair bit)

[chalin]

Btw, thanks for your answer @caitp. API docs have been updated via #842.