Config of error message : Failure when defined via function + constraint is outOfRange or wrongLength

[er314]

When configuring custom error message, for constraint outOfRange or wrongLength,
if it's done via a function (instead of via plain string),
then it fails.
ex : cfg.messages.outOfRange.over = function (field) { ... return myMessage; }

• Cause : getErrorMessage supports both String + Function, but, for outOfRange and wrongLength, it calls String-only methods, without checking the input type :

/**
* Get the error message test
* @param {Node} field The field to get an error message for
* @param {Object} errors The errors on the field
* @param {Object} settings The plugin settings
* @return {:point_right:String|Function:point_left:} The error message
*/
var getErrorMessage = function (field, errors, settings) {
...
// Numbers that are out of range
if (errors.outOfRange) {
return messages.outOfRange[errors.outOfRange].:point_right:replace:point_left:('{max}', ...

• Solution : Perform the String-only text replacement only if input type is String.
  See pull-request Proposed fix for Issue #57 #58 for proposed fix.

[cferdinandi]

sorry y'all, this has just not been a priority for me at the moment. 😔

[cferdinandi]

I mean, I'm always open to PRs on this free software 😉