Having validateAll throw an exception is a bad idea

Versions:

• VueJs: 2.3.3
• Vee-Validate: 2.0.0-rc.3

Description:

Because the validateAll methods throws an exception, I’m forced to have .catch(() => { }) littered through my code otherwise the exception isn’t caught and I get an uncaught error. The exception isn’t interesting to me because the error messages are rendered in my template automatically using the errorBag. I shouldn’t be forced to deal with this error.

The purpose of this method is to validate all fields. It should only throw an exception if there was an unexpected problem when trying to run validation. A field not being valid isn’t an error. it’s an expected outcome. So why are people forced to have a (possibly empty) catch block in there code for expected outcomes?

[Neve12ende12]

@rstuart85 @logaretm

Since validateAll() returns a promise, couldn’t we use .done() and .fail() or would that present the same problem that caused you to get rid of .catch()?

[pachecoder]

validateForm(scope) {
        this.$validator.validateAll(scope)
        .then(() => {
           alert('success')
        })
        .catch(() => { })
      }

Hi @logaretm why i get this error when i’m handling my promises?