Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

component architecture results in many isolate scopes #15634

Closed
wants to merge 1 commit into from
Closed

component architecture results in many isolate scopes #15634

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 5 additions & 5 deletions docs/content/guide/scope.ngdoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,12 +109,12 @@ to test the behavior without being distracted by the rendering details.
## Scope Hierarchies

Each Angular application has exactly one {@link ng.$rootScope root scope}, but
may have several child scopes.
may have many child scopes.

The application can have multiple scopes, because some {@link guide/directive directives} create
new child scopes (refer to directive documentation to see which directives create new scopes).
When new scopes are created, they are added as children of their parent scope. This creates a tree
structure which parallels the DOM where they're attached.
The application can have multiple scopes, because some {@link guide/directive directives} and all
components create new child scopes (refer to directive documentation to see which directives create
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"components" is misleading. Components are just shorthand for a specific directive notation. Please expand to "component directives" and add a link to the component guide.

And also, can you please add a link to $compile for "directive documentation"? Because that's where the options are defined.

new scopes). When new scopes are created, they are added as children of their parent scope. This
creates a tree structure which parallels the DOM where they're attached.

When Angular evaluates `{{name}}`, it first looks at the scope associated with the given
element for the `name` property. If no such property is found, it searches the parent scope
Expand Down