Sonu Kapoor 88a235de3a fix(forms): handle numeric values properly in the validator (#36157) ...

Previously, the behavior of the `minLength` and `maxLength` validators
caused confusion, as they appeared to work with numeric values but
did not in fact produce consistent results. This commit fixes the issue
by skipping validation altogether when a numeric value is used.

BREAKING CHANGES:

* The `minLength` and `maxLength` validators now verify that a value has
numeric `length` property and invoke validation only if that's the case.
Previously, falsey values without the length property (such as `0` or
`false` values) were triggering validation errors. If your code relies on
the old behavior, you can include other validators such as [min][1] or
[requiredTrue][2] to the list of validators for a particular field.

[1]: https://angular.io/api/forms/Validators#min
[2]: https://angular.io/api/forms/Validators#requiredTrue

Closes #35591

PR Close #36157

2020-05-05 11:50:00 -07:00

..

src

fix(forms): handle numeric values properly in the validator (#36157)

2020-05-05 11:50:00 -07:00

test

fix(forms): handle numeric values properly in the validator (#36157)

2020-05-05 11:50:00 -07:00

BUILD.bazel

build: provide full paths to ts_api_guardian_test_npm_package and ts_api_guardian_test (#36034)

2020-03-12 09:49:00 -07:00

index.ts

refactor: move angular source to /packages rather than modules/@angular

2017-03-08 16:29:27 -08:00

package.json

build(packaging): add repository.directory field to package.jsons (#27544)

2020-02-25 13:12:45 -08:00

PACKAGE.md

docs: more form overview edits (#25663)

2018-09-25 18:48:15 -07:00

public_api.ts

build: publish tree of files rather than FESMs (#18541)

2017-08-31 15:34:50 -07:00