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

Commit 4b91042

Browse files
committed
docs(form): remove mention of interpolated control names not being supported
The docs state that interpolation cannot be used in control names. This used to be true, but not anymore. Closes #13520
1 parent a9ecde1 commit 4b91042

File tree

1 file changed

+3
-7
lines changed

1 file changed

+3
-7
lines changed

src/ng/directive/form.js

+3-7
Original file line numberDiff line numberDiff line change
@@ -318,13 +318,9 @@ function FormController(element, attrs, $scope, $animate, $interpolate) {
318318
*
319319
* In Angular, forms can be nested. This means that the outer form is valid when all of the child
320320
* forms are valid as well. However, browsers do not allow nesting of `<form>` elements, so
321-
* Angular provides the {@link ng.directive:ngForm `ngForm`} directive which behaves identically to
322-
* `<form>` but can be nested. This allows you to have nested forms, which is very useful when
323-
* using Angular validation directives in forms that are dynamically generated using the
324-
* {@link ng.directive:ngRepeat `ngRepeat`} directive. Since you cannot dynamically generate the `name`
325-
* attribute of input elements using interpolation, you have to wrap each set of repeated inputs in an
326-
* `ngForm` directive and nest these in an outer `form` element.
327-
*
321+
* Angular provides the {@link ng.directive:ngForm `ngForm`} directive, which behaves identically to
322+
* `form` but can be nested. Nested forms can be useful, for example, if the validity of a sub-group
323+
* of controls needs to be determined.
328324
*
329325
* # CSS classes
330326
* - `ng-valid` is set if the form is valid.

0 commit comments

Comments
 (0)