Dylan Hunn 7180ec9e7c fix(forms): changes to status not always being emitted to statusChanges observable for async validators. (#42553) ... When a FormControl, FormArray, or FormGroup is first constructed, if an async validator is attached, the `statusChanges` observable should receive a message when the validator complete (i.e. pending -> valid/invalid). If the validator was provided as part of the constructor options, it was not fired at construction time, which is fixed in this PR. Fixes #35309. PR Close #42553		2021-06-14 09:57:57 -07:00
..
directives	feat(forms): undo revert and add ng-submitted class to forms that have been submitted. (#42132) (#42132)	2021-06-08 14:02:29 -07:00
directives.ts	perf(forms): make RadioControlRegistry class tree-shakable (#41126)	2021-03-16 09:35:14 -07:00
form_builder.ts	perf(forms): make FormBuilder class tree-shakable (#41126)	2021-03-16 09:35:14 -07:00
form_providers.ts	perf(forms): make RadioControlRegistry class tree-shakable (#41126)	2021-03-16 09:35:14 -07:00
forms.ts	feat(forms): introduce min and max validators (#39063)	2021-02-08 09:34:50 -08:00
model.ts	fix(forms): changes to status not always being emitted to statusChanges observable for async validators. (#42553)	2021-06-14 09:57:57 -07:00
validators.ts	perf(forms): avoid direct references to the Validators class (#41189)	2021-03-15 11:12:55 -07:00
version.ts	docs: fix package name in version.ts files in different packages (#41208)	2021-05-10 10:26:34 -04:00