ng-enabled="attribute.value === true"
ng-disabled="!(attribute.value === true)"
The reason why there is no
ngEnabled directive in Angular is rather semantical - there is simply nothing corresponding to it in HTML specification. At the same time there is already
ngDisabled directive that works with
disabled attribute. For the same reason, there is no
ngUnchecked directive, because there is already
ngChecked that sets/removes
Now, the reasonable question: why we have both
ngHide then? Well it's just for convenience in this case I guess, because having both
ngHide is not more confusing than
ngShow alone, but at the same time it's very handy to have both.