Add validatorName to the list of error messages

[mattruby]

It would be nice to be able to style error messages based on the validation type. Perhaps the return type could be set as on option.

Today:
{password: ["Password can't be blank"]}

Suggestion:
{password: [{validatorName:"length", errorMessage: "Password is too short (minimum is 6 characters)", value: "pass"}]}

The catalyst for wanting this change is a warning state where I suggest an email correction: "Did you mean comcast.net in place of comcast.com". This message would be interactive with a link to the corrected address.

[ansman]

That sounds like a good idea.

I'm on vacation right now but I'll look in to this when I get back in January.

On Thu, Dec 18, 2014 at 7:48 AM, mattruby notifications@github.com
wrote:

It would be nice to be able to style error messages based on the validation type. Perhaps the return type could be set as on option.
Today:
{password: ["Password can't be blank"]}
Suggestion:
{password: [{validatorName:"length", errorMessage: "Password is too short (minimum is 6 characters)", value: "pass"}]}

The catalyst for wanting this change is a warning state where I suggest an email correction: "Did you mean comcast.net in place of comcast.com". This message would be interactive with a link to the corrected address.

Reply to this email directly or view it on GitHub:
#14

[tamtakoe]

phoneNumber: [{
    required: true;
    message:  'isEmpty'
}, {
    pattern: '[0-9]+',
    message: 'notInt'
}, {
    length:  11,
    message: 'invalidLength'
}, {
    unique:  'phoneNumber',
    model:   User,
    message: 'exists'
}]

[ansman]

Released in 0.7.0

You can now to the following:

var constraints = {
  username: {
    presence: true
  }
};
validate({}, constraints, {format: "detailed"});
// => [{
//   "attribute": "username",
//   "validator": "presence",
//   "options": true,
//   "error": "Username can't be blank"
// }]