You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had an idea to add a directive called ng-id that would work just like #name does in Angular 2. It would be an easy migration of find/replace. It would work as follows:
<inputng-id="userName">
userName would be added to the scope.
Unknowns: I'm not sure if this is a variable that's limited to the template html only or if it can be accessed by component controllers. I'm pretty sure its template only, so let's start there.
The text was updated successfully, but these errors were encountered:
Once we have ng-id, we could add a template helper that supports converting #name into ng-id="name", so we could support the real syntax as well. This is similar to how we currently convert ng-content to ng-transclude before registering the component as a directive.
Would need to have a pretty high priority so that all other directives could reference the element in their expressions. The current highest priorities are ngSwitch at 1200. I'm thinking going to 1500 would be good. There's no good reason to not set this very high as it's pretty innocuous.
I had an idea to add a directive called
ng-id
that would work just like#name
does in Angular 2. It would be an easy migration of find/replace. It would work as follows:userName
would be added to the scope.Unknowns: I'm not sure if this is a variable that's limited to the template html only or if it can be accessed by component controllers. I'm pretty sure its template only, so let's start there.
The text was updated successfully, but these errors were encountered: