I'm okay with making the email validation configurable, but I really want to avoid adding more options. Partly because there are too many already, partly because this would tie in the method even more into the core.

To take a step back, why do you need this as an option? Could you override the email method as needed? Or use a custom email method when you need to the default on the same page?

To take a step back, why do you need this as an option? Could you override the email method as needed? Or use a custom email method when you need to the default on the same page?

I could of course use a separate email validation method. IMO email validation will only be different in the email format and per definition will not have other differences, so I decided to go this road.

In case email method validation itself would be a separate plugin, how would I define options for it?
Maybe we can find a way which later on will be BC with what we introduce now.

Per se, I would love to reduce the jquery-validation core to less lines and have a built which only contains the rules I really need for a certain app.

As you already know, email pattern issues are the most reported errors in this tracker, therefore solving the issue using a config param is a must have for a lot of our users. (I am not saying it has to be a option passed to the validator).

Is separating the core from the actual methods a step which requires a BC break or do you plan to solve it in a BC compatible way?

@jzaefferer what do you think, how to proceed?

I just tried the other way you proposed.

In case we promote the $.validator.methods.<myRule> properties to be part of the public api, I could override the native-email method with my custom regex without providing another option.

example:

// setup the validation
// ...
// place my override
$.validator.methods.email = function( value, element ) { 
  return this.optional( element ) || /whatEverRegexILike/.test( value ); 
}

@jzaefferer wdyt?

That looks good to me.

will open a doc PR then, thanks.

here we go
#1530
jquery-validation/validation-content#14