angular-docs-cn/aio/content/guide/attribute-directives.md

@title Attribute Directives

@intro Attribute directives attach behavior to elements.

@description

An Attribute directive changes the appearance or behavior of a DOM element.

Contents

• Directives overview
• Build a simple attribute directive
• Apply the attribute directive to an element in a template
• Respond to user-initiated events
• Pass values into the directive with an @Input data binding
• Bind to a second property

Try the .

Directives overview

There are three kinds of directives in Angular:

1. Components—directives with a template.
2. Structural directives—change the DOM layout by adding and removing DOM elements.
3. Attribute directives—change the appearance or behavior of an element, component, or another directive.

Components are the most common of the three directives. You saw a component for the first time in the QuickStart guide.

Structural Directives change the structure of the view. Two examples are NgFor and NgIf. Learn about them in the Structural Directives guide.

Attribute directives are used as attributes of elements. The built-in NgStyle directive in the Template Syntax guide, for example, can change several element styles at the same time.

Build a simple attribute directive

An attribute directive minimally requires building a controller class annotated with @Directive, which specifies the selector that identifies the attribute. The controller class implements the desired directive behavior.

This page demonstrates building a simple myHighlight attribute directive to set an element's background color when the user hovers over that element. You can apply it like this:

Write the directive code

Follow the setup instructions for creating a new local project named attribute-directives.

Create the following source file in the indicated folder:

The import statement specifies symbols from the Angular core:

1. Directive provides the functionality of the @Directive decorator.
2. ElementRef injects into the directive's constructor so the code can access the DOM element.
3. Input allows data to flow from the binding expression into the directive.

Next, the @Directive decorator function contains the directive metadata in a configuration object as an argument.

@Directive requires a CSS selector to identify the HTML in the template that is associated with the directive. The CSS selector for an attribute is the attribute name in square brackets. Here, the directive's selector is [myHighlight]. Angular locates all elements in the template that have an attribute named myHighlight.

### Why not call it "highlight"?

Though *highlight* is a more concise name than *myHighlight* and would work,
a best practice is to prefix selector names to ensure
they don't conflict with standard HTML attributes.
This also reduces the risk of colliding with third-party directive names.

Make sure you do **not** prefix the `highlight` directive name with **`ng`** because
that prefix is reserved for Angular and using it could cause bugs that are difficult to diagnose. 
For a simple demo, the short prefix, `my`, helps distinguish your custom directive.

After the @Directive metadata comes the directive's controller class, called HighlightDirective, which contains the logic for the directive. Exporting HighlightDirective makes it accessible to other components.

Angular creates a new instance of the directive's controller class for each matching element, injecting an Angular ElementRef into the constructor. ElementRef is a service that grants direct access to the DOM element through its nativeElement property.

Apply the attribute directive

To use the new HighlightDirective, create a template that applies the directive as an attribute to a paragraph (<p>) element. In Angular terms, the <p> element is the attribute host.

Put the template in its own app.component.html file that looks like this:

Now reference this template in the AppComponent:

Next, add an import statement to fetch the Highlight directive and add that class to the declarations NgModule metadata. This way Angular recognizes the directive when it encounters myHighlight in the template.

Now when the app runs, the myHighlight directive highlights the paragraph text.

### Your directive isn't working?

Did you remember to add the directive to the `declarations` attribute of `@NgModule`? 
It is easy to forget!
Open the console in the browser tools and look for an error like this:


<code-example format="nocode">
  EXCEPTION: Template parse errors:
    Can't bind to 'myHighlight' since it isn't a known property of 'p'.

</code-example>



Angular detects that you're trying to bind to *something* but it can't find this directive
in the module's `declarations` array.
After specifying `HighlightDirective` in the `declarations` array,
Angular knows it can apply the directive to components declared in this module.

To summarize, Angular found the myHighlight attribute on the <p> element. It created an instance of the HighlightDirective class and injected a reference to the <p> element into the directive's constructor which sets the <p> element's background style to yellow.

Respond to user-initiated events

Currently, myHighlight simply sets an element color. The directive could be more dynamic. It could detect when the user mouses into or out of the element and respond by setting or clearing the highlight color.

Begin by adding HostListener to the list of imported symbols; add the Input symbol as well because you'll need it soon.

Then add two eventhandlers that respond when the mouse enters or leaves, each adorned by the HostListener decorator.

The @HostListener decorator lets you subscribe to events of the DOM element that hosts an attribute directive, the <p> in this case.

Of course you could reach into the DOM with standard JavaScript and and attach event listeners manually.
There are at least three problems with _that_ approach:

1. You have to write the listeners correctly.
1. The code must *detach* the listener when the directive is destroyed to avoid memory leaks.
1. Talking to DOM API directly isn't a best practice.

The handlers delegate to a helper method that sets the color on the DOM element, el, which you declare and initialize in the constructor.

Here's the updated directive in full:

Run the app and confirm that the background color appears when the mouse hovers over the p and disappears as it moves out.

Pass values into the directive with an @Input data binding

Currently the highlight color is hard-coded within the directive. That's inflexible. In this section, you give the developer the power to set the highlight color while applying the directive.

Start by adding a highlightColor property to the directive class like this:

{@a input}

Binding to an @Input property

Notice the @Input decorator. It adds metadata to the class that makes the directive's highlightColor property available for binding.

It's called an input property because data flows from the binding expression into the directive. Without that input metadata, Angular rejects the binding; see below for more about that.

Try it by adding the following directive binding variations to the AppComponent template:

Add a color property to the AppComponent.

Let it control the highlight color with a property binding.

That's good, but it would be nice to simultaneously apply the directive and set the color in the same attribute like this.

The [myHighlight] attribute binding both applies the highlighting directive to the <p> element and sets the directive's highlight color with a property binding. You're re-using the directive's attribute selector ([myHighlight]) to do both jobs. That's a crisp, compact syntax.

You'll have to rename the directive's highlightColor property to myHighlight because that's now the color property binding name.

This is disagreeable. The word, myHighlight, is a terrible property name and it doesn't convey the property's intent.

{@a input-alias}

Bind to an @Input alias

Fortunately you can name the directive property whatever you want and alias it for binding purposes.

Restore the original property name and specify the selector as the alias in the argument to @Input.

Inside the directive the property is known as highlightColor. Outside the directive, where you bind to it, it's known as myHighlight.

You get the best of both worlds: the property name you want and the binding syntax you want:

Now that you're binding to highlightColor, modify the onMouseEnter() method to use it. If someone neglects to bind to highlightColor, highlight in red:

Here's the latest version of the directive class.

Write a harness to try it

It may be difficult to imagine how this directive actually works. In this section, you'll turn AppComponent into a harness that lets you pick the highlight color with a radio button and bind your color choice to the directive.

Update app.component.html as follows:

Revise the AppComponent.color so that it has no initial value.

Here are the harness and directive in action.

Bind to a second property

This highlight directive has a single customizable property. In a real app, it may need more.

At the moment, the default color—the color that prevails until the user picks a highlight color—is hard-coded as "red". Let the template developer set the default color.

Add a second input property to HighlightDirective called defaultColor:

Revise the directive's onMouseEnter so that it first tries to highlight with the highlightColor, then with the defaultColor, and falls back to "red" if both properties are undefined.

How do you bind to a second property when you're already binding to the myHighlight attribute name?

As with components, you can add as many directive property bindings as you need by stringing them along in the template. The developer should be able to write the following template HTML to both bind to the AppComponent.color and fall back to "violet" as the default color.

Angular knows that the defaultColor binding belongs to the HighlightDirective because you made it public with the @Input decorator.

Here's how the harness should work when you're done coding.

Summary

This page covered how to:

• Build an attribute directive that modifies the behavior of an element.
• Apply the directive to an element in a template.
• Respond to events that change the directive's behavior.
• Bind values to the directive.

The final source code follows:

You can also experience and download the .

Appendix: Why add @Input?

In this demo, the hightlightColor property is an input property of the HighlightDirective. You've seen it applied without an alias:

You've seen it with an alias:

Either way, the @Input decorator tells Angular that this property is public and available for binding by a parent component. Without @Input, Angular refuses to bind to the property.

You've bound template HTML to component properties before and never used @Input. What's different?

The difference is a matter of trust. Angular treats a component's template as belonging to the component. The component and its template trust each other implicitly. Therefore, the component's own template may bind to any property of that component, with or without the @Input decorator.

But a component or directive shouldn't blindly trust other components and directives. The properties of a component or directive are hidden from binding by default. They are private from an Angular binding perspective. When adorned with the @Input decorator, the property becomes public from an Angular binding perspective. Only then can it be bound by some other component or directive.

You can tell if @Input is needed by the position of the property name in a binding.

• When it appears in the template expression to the right of the equals (=), it belongs to the template's component and does not require the @Input decorator.

• When it appears in square brackets () to the left of the equals (=), the property belongs to some other component or directive; that property must be adorned with the @Input decorator.

Now apply that reasoning to the following example:

• The color property in the expression on the right belongs to the template's component. The template and its component trust each other. The color property doesn't require the @Input decorator.

• The myHighlight property on the left refers to an aliased property of the HighlightDirective, not a property of the template's component. There are trust issues. Therefore, the directive property must carry the @Input decorator.