docs: move helpful alert regarding built-in directives to more logical place (#42226)
Moving the helpful alert expressing that built-in directives use public APIs to be under the heading about built-in directives generally makes the content in the alert more related to its surroundings than its previous location within the ng-for section. Closes #38525 PR Close #42226
This commit is contained in:
parent
30c461d862
commit
4d56c10584
|
@ -31,6 +31,13 @@ The most common attribute directives are as follows:
|
|||
* [`NgStyle`](guide/built-in-directives#ngstyle)—adds and removes a set of HTML styles.
|
||||
* [`NgModel`](guide/built-in-directives#ngModel)—adds two-way data binding to an HTML form element.
|
||||
|
||||
<div class="alert is-helpful">
|
||||
|
||||
Built-in directives use only public APIs.
|
||||
They do not have special access to any private APIs that other directives can't access.
|
||||
|
||||
</div>
|
||||
|
||||
{@a ngClass}
|
||||
## Adding and removing classes with `NgClass`
|
||||
|
||||
|
@ -269,13 +276,6 @@ In the following illustration of the `trackBy` effect, **Reset items** creates n
|
|||
<img src="generated/images/guide/built-in-directives/ngfor-trackby.gif" alt="Animation of trackBy">
|
||||
</div>
|
||||
|
||||
<div class="alert is-helpful">
|
||||
|
||||
Built-in directives use only public APIs.
|
||||
They do not have special access to any private APIs that other directives can't access.
|
||||
|
||||
</div>
|
||||
|
||||
{@a ngcontainer}
|
||||
|
||||
## Hosting a directive without a DOM element
|
||||
|
|
Loading…
Reference in New Issue