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
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Narretz
suggested changes
Jan 23, 2017
| 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 |
There was a problem hiding this comment.
"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.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
docs update
What is the current behavior? (You can also link to an open issue here)
na
What is the new behavior (if this is a feature change)?
na
Does this PR introduce a breaking change?
no
Please check if the PR fulfills these requirements
Other information: