Skip to content
This repository was archived by the owner on Dec 4, 2017. It is now read-only.

docs(architecture): remove reference to directives in component metadata #2481

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 1 addition & 6 deletions public/docs/ts/latest/guide/architecture.jade
Original file line number Diff line number Diff line change
Expand Up @@ -252,7 +252,7 @@ block ts-decorator
Here are a few of the possible `@Component` configuration options:

:marked
- `moduleId: module.id`: sets the base for module-relative loading of the `templateUrl`.
- `moduleId`: sets the source of the base address (`module.id`) for module-relative URLs such as the `templateUrl`.

- `selector`: CSS selector that tells Angular to create and insert an instance of this component
where it finds a `<hero-list>` tag in *parent* HTML.
Expand All @@ -261,11 +261,6 @@ block ts-decorator

- `templateUrl`: module-relative address of this component's HTML template, shown [above](#templates).

- `directives`: !{_array} of the components or directives that *this* template requires.
In the last line of `hero-list.component.html`, Angular inserts a `HeroDetailComponent`
in the space indicated by `<hero-detail>` tags.
Angular does so only if `HeroDetailComponent` is in this `directives` !{_array}.

- `providers`: !{_array} of **dependency injection providers** for services that the component requires.
This is one way to tell Angular that the component's constructor requires a `HeroService`
so it can get the list of heroes to display.
Expand Down