There are a few steps that need to be done to implement client side custom validation:
1. Make our custom validation class (see my previous post for the codes example) inherits from IClientValidatable and implement its GetClientValidationRules method.
public class SumIntegers : ValidationAttribute, IClientValidatable { . . . public IEnumerable<ModelClientValidationRule> GetClientValidationRules(ModelMetadata metadata, ControllerContext context) { ModelClientValidationRule rule = new ModelClientValidationRule(); //specify a name for the custom validation rule.ValidationType = "sumintegers"; //pass an error message to be used rule.ErrorMessage = FormatErrorMessage(metadata.GetDisplayName()); //pass parameter(s) that need to be used when validating rule.ValidationParameters.Add("sum", _sum); yield return rule; } }To do this we need to add a reference to System.Web.Mvc namespace in the class file.
Below is the html generated from the ModelClientValidationRule properties set above.
<input type="text" value="" name="CSVInput" id="CSVInput" data-val-sumintegers-sum="20" data-val-sumintegers="custom error message for CSVInput" data-val="true" class="text-box single-line valid">As we can see, the properties are put into data-val attributes. The attribute data-val-[validation_name] contains the error message, where [validation_name] is the ValidationType property's value we set above. Each passed parameter is put into data-val-[validation_name]-[parameter_name] attribute.
2. Write a jQuery validation adapter.
The adapter is used to retrieve the data-val attributes with their values and translate them into a format that jQuery validation can understand. So this adapter is helping us to easily implement our unobtrusive client side validation.
The adapter has several methods that we can use:
- addBool - creates an adapter for a validation rule that is 'on' or 'off', it requires no additional parameters
- addSingleVal- creates an adapter for a validation rule that needs to retrieve a single parameter value
- addMinMax - creates an adapter that maps to a set of validation rules, one that checks for a minimum value and the other checks for a maximum value
- add - used to create a custom adapter if we cannot use one of the methods above. We can use this if the adapter requires additional parameters or extra setup code.
In our case, addSingleVal is the best one to use.
// first parameter is the adapter name which should match with the value of ValidationType // property of ModelClientValidationRule set on the server side // second parameter is the parameter name added to ValidationParameters property of // ModelClientValidationRule on the server side $.validator.unobtrusive.adapters.addSingleVal("sumintegers", "sum");
3. Write the jQuery validator.
We do this through a method called addMethod that belongs to jQuery validator object.
// first parameter is the validator name which should match with the adapter name // (which is also the same as the value of ValidationType) // second parameter is the validation function to be invoked $.validator.addMethod("sumintegers", // the validation function's first parameter is the input value, second is the input element // and the third one is the validation parameter or an array of validation parameters passed function (inputValue, inputElement, sum) { var returnValue = true; if (inputValue) { var total = 0; try { $.each(inputValue.split(','), function () { total += parseInt(this); }); } catch (err) { returnValue = false; } if (total != sum) { returnValue = false; } } return returnValue; });
Say we put the scripts from step two and three in a single file called CustomScripts.js. Below is all the scripts that we have written:
/// <reference path="jquery-1.4.4.js" /> /// <reference path="jquery.validate.js" /> /// <reference path="jquery.validate.unobtrusive.js" /> if ($.validator && $.validator.unobtrusive) { $.validator.unobtrusive.adapters.addSingleVal("sumintegers", "sum"); $.validator.addMethod("sumintegers", function (inputValue, inputElement, sum) { var returnValue = true; if (inputValue) { var total = 0; try { $.each(inputValue.split(','), function () { total += parseInt(this); }); } catch (err) { returnValue = false; } if (total != sum) { returnValue = false; } } return returnValue; }); }The first three lines are references put to have IntelliSense works in our codes. Make sure the paths are correct.
4. Finally, include jquery.validate, jquery.validate.unobtrusive and our custom scripts files on the page to render.
<script src="@Url.Content("~/Scripts/jquery.validate.min.js")" type="text/javascript"></script> <script src="@Url.Content("~/Scripts/jquery.validate.unobtrusive.min.js")" type="text/javascript"></script> <script src="@Url.Content("~/Scripts/CustomScripts.js")"></script>
Tips: at the first time this validation will fire after the input lost focus but after that it will fire after each key press. This is the default behaviour of other built-in validators. If you are not happy with this and would like the validation to always fire only when the input lost focus then you need to add one of these scripts:
// if only for the specific input field $(document).ready(function () { $("input#CSVInput").keyup(function () { return false; }); } // or for all input fields // never put this inside document ready function $.validator.setDefaults({ onkeyup: false })
Reference:
Professional ASP.NET MVC 3 - Jon Galloway, Phil Haack, Brad Wilson, K. Scott Allen
4 comments:
Thanks for this. I learned a lot.
Thank you so much. The "Tips" section is the solution I was looking for ! :)
On additional Note, I was looking for the solution of model data annotation attributes for validation only on lost focus. What worked for me was:
$(formSelector).removeData("validator");
$(formSelector).removeData("unobtrusiveValidation");
//Suppressing the validator during keyup and lost focus event
$.validator.setDefaults({
onkeyup: false,
onfocusout: false
});
$.validator.unobtrusive.parse(formSelector);
Aby_The_One, you welcome and thank you for sharing your solution.
Post a Comment