Buggy behavior when specifying invalid rules/methods

[joshribakoff]

If you put a typo in your rules like accidentally putting:

rules: {
  myField: { require:true }
}

Instead of putting:

rules: {
  myField: { required:true }
}

You will observe undefined behavior. Obscure stack traces about calling .call() on undefined, and forms submitting even though they are invalid.

If I put a typo, I would expect an exception that says "the rule 'require' for the element 'myField' has no corresponding method" and for the field to be marked as invalid & prevent submission.

In debugging this, it seems to confuse a lot of users. There are tons of unanswered questions on stack overflow stemming from this issue.

[GiuseppeMobijay]

It happen also on not found input name in the form.

rules: {
myFiel: {required:true}
}

[jzaefferer]

You can use the debug option to get better error messages on the console.