ng-model vs. child $scope created by translate-attr-placeholder

I really searched a lot to try finding some answers, sorry if it is duplicated somehow.

Today I tried to use ng-translate with placeholder using the translate-attr-placeholder directive.

It worked, however, this directive is creating a child $scope and, because of that, the ng-model creates an object inside of each directive $scope, instead of creating in the controller’s $scope:

Example:

<input type="text" ng-model="auth.username" translate translate-attr-placeholder="Username"/>
<input type="password" ng-model="auth.password" translate translate-attr-placeholder="Password"/>

<button ng-click="login(auth)">LOG IN</button>

In this case, the login function receives an undefined auth.

If it’s the normal behavior, no problem, of course that are many ways to deal with nested $scope. I just would like to know if I’m using it wrong?

Thanks a lot!

[rajush]

This is something I faced too. I had a similar question posted here: [https://github.com/angular-translate/angular-translate/issues/874]

For now, I’m using filter within the expression of the placeholder placeholder="{{ 'text' | translate }}" which binds the scope to the controller, until I find a way to figure it out. I hope there is way to solve this without using a filter.

Thanks!

[knalli]

Right. Currently we cannot resolve this without a scope.

Highly recommended: Use always expressions with dots. The controllerAs approach is a very good way! The other way is using the filter.