Initial isFieldValid returns true when field is empty and uses required validator. about aspnet-client-validation

[dahlbyk]

You're absolutely correct that the debounce is making an otherwise synchronous validation async so it immediately returns true. We should fix that.

It's worth mentioning here that returning the cached value is what happens "by design" if there's a remote or other Promise-returning validator involved. Ideally the method would return a Promise<bool>, but that's a breaking change. Maybe v2?

That might still make the return value unreliable if debounce is not 0 though.

This is also correct, and we should fix that.

1. validateField() should always call the underlying validator, undebounced.
2. Only the change/input handler should be debounced.

I actually have a branch in progress (for #100) that's adjusting how the callback is wired/unwired, so I can include this fix in that change.

[RyanONeill1970]

Well, thank you very much. Sorry to pile stuff on to your plate.

[dahlbyk]

Give this a try? #110

[RyanONeill1970]

Not sure if Phil has made his changes from review. Let me know when the review is good to test.

[dahlbyk]

I fixed the bug Phil found. 👍 Please test!