docs: clarify that @for doesn't support break/continue (angular#59533)

jelbourn · kirjs · commit c38ea0767e50 · 2025-01-15T12:00:21.000-05:00
We recently saw some confusion around this, so it's worth adding a sentence to clarify PR Close angular#59533
diff --git a/adev/src/content/guide/templates/control-flow.md b/adev/src/content/guide/templates/control-flow.md
@@ -50,6 +50,8 @@ A typical `@for` loop looks like:
 }
 ```
 
+Angular's `@for` block does not support flow-modifying statements like JavaScript's `continue` or `break`.
+
 ### Why is `track` in `@for` blocks important?
 
 The `track` expression allows Angular to maintain a relationship between your data and the DOM nodes on the page. This allows Angular to optimize performance by executing the minimum necessary DOM operations when the data changes.
diff --git a/tools/manual_api_docs/blocks/for.md b/tools/manual_api_docs/blocks/for.md
@@ -19,6 +19,8 @@ but there are performance advantages of using a regular `Array`.
 You can optionally include an `@empty` section immediately after the `@for` block content. The
 content of the `@empty` block displays when there are no items.
 
+Angular's `@for` block does not support flow-modifying statements like JavaScript's `continue` or `break`.
+
 ### `track` and objects identity
 
 The value of the `track` expression determines a key used to associate array items with the views in

Original file line number	Diff line number	Diff line change
@@ -50,6 +50,8 @@ A typical `@for` loop looks like:
`50`	`50`	`}`
`51`	`51`	```
`52`	`52`
	`53`	+Angular's `@for` block does not support flow-modifying statements like JavaScript's `continue` or `break`.
	`54`	`+`
`53`	`55`	### Why is `track` in `@for` blocks important?
`54`	`56`
`55`	`57`	The `track` expression allows Angular to maintain a relationship between your data and the DOM nodes on the page. This allows Angular to optimize performance by executing the minimum necessary DOM operations when the data changes.