Skip to main content

Simple client side validation library

    
Client side validation has never been easy..



Include jQuery and the validator.js 

<script src="http://code.jquery.com/jquery-1.11.3.min.js"></script> <script src="../validate.js"></script>

Simple validation

<form id="myForm"> <label>User Name <span class="red-star">*</span> </label>
<input type="text" name="userName" class="validate-required" />
<br />
<label>Password <span class="red-star">*</span></label>
<input type="password" name="password" class="validate-required" />
<br />
<input type="submit" value="Login" />
</form>
<script type="text/javascript">
$(function () {
validator.initValidationEvents('myForm');
validator.showError = function(element,errorMessage){
$(element).notify(
errorMessage,
{
position:"right",
autoHide: false,
clickToHide: false
}
);
};
validator.hideError = function(element){
$(element).notify('notify-hide');
};
});
</script>

Validating regex


<form id="myForm"> <label>User Name <span class="red-star">*</span> </label>
<input type="text" name="userName"
class="validate-required validate-regexp"
data-regexp='^(ftp|http|https):\/\/[^ "]+$'
data-validate-regexp="Please provide a valid url." />
<br />
<label>Password <span class="red-star">*</span></label>
<input type="password" name="password" class="validate-required" />
<br />
<input type="submit" value="Login" />
</form>
<script type="text/javascript">
/*
You can give any regexp as data-regexp and provide data-validate-regexp as the validation human readable version.
This way you can handle most of the validations out there.
If you need more customization, then you can go for validator.addMethod ( I have provided a separate example for this 04-add-custom-methods.html )
*/
$(function () {
validator.initValidationEvents('myForm');
});
</script>

Validating without a form

<div id="myDiv"> <label>User Name <span class="red-star">*</span> </label> <input type="text" name="userName" class="validate-required" />
<br />
<label>Password <span class="red-star">*</span></label>
<input type="password" name="password" class="validate-required" />
<br />
<input type="button" id="loginButton" value="Login" />
</div>
<script type="text/javascript">
$(function () {
/*
Default case of initValidationEvents method is expecting the page to have a form and a button with type="submit".
But in this case we just have a div container and a button with type="button".
So we are passing a dummy function as an argument to disable submit event handler.
*/
validator.initValidationEvents('myDiv',function(){});
$('#loginButton').click(function(){
if(validator.isValidForm('myDiv')){
alert('your form is valid :D');
} else {
alert('your form is not valid !!!!! :(')
}
})
});
</script>

https://github.com/chanaka3d/validator

Displaying a resource in the WSO2 registry with jaggery


var carbon = require('carbon');
    var server = new carbon.server.Server();
    var options = {
        username: 'admin',
        tenantId: -1234
    };
    var reg = new carbon.registry.Registry(server, options);
    var path = '/_system/es/cartoon001gossiplankanews.png';
    var resource = reg.get(path);
    response.contentType = resource.mediaType;
    print(reg.content(path));

Comments

Anonymous said…
This comment has been removed by the author.

Popular posts from this blog

Overriding default look and feel of GREG - 5.3.0

Following list explains what are the best approach for different use cases. 1 ) - You created a new asset type, and you need to change the look and feel of the details page in the listing page just for that new asset type. To create a new asset type you need to login to the carbon console (username:admin, password:admin) https:// :9443/carbon/ Navigate to Extensions > Configure > Artifacts Click "Add new Artifact" link at the bottom of the page. By default in the "Generic Artifact" area "application" asset type is loaded. Note the shortName="applications" in the root node. "applications" is the name of the asset type. Browse in to /repository/deployment/server/jaggeryapps/store/extensions/assets Create a folder with name "applications"    Now we can override the files in /repository/deployment/server/jaggeryapps/store/extensions/app/greg-store-defaults   Since we are overriding the details page we need to...

Role of GREG permission-mappings.xml

 GREG has a permission-mapping.xml. We can find it at /home/chanaka/Desktop/greg/wso2greg-5.2.0/repository/conf/etc/permission-mappings.xml Each entry has three attributes. managementPermission resourcePermission resourcePaths  Ex: managementPermission="/permission/admin/manage/resources/govern/server/list" resourcePermission="http://www.wso2.org/projects/registry/actions/get" resourcePaths="/_system/governance/trunk/servers" /> There are default configurations in this file. These entries are mapping each permission in the permission tree in to resource paths and assign them permissions. With the above line in the permission-mappings.xml, an admin user who assign the permission " /permission/admin/manage/resources/govern/server/list " will be able to do get operations on registry resources stored at " /_system/governance/trunk/servers ". We can provide multiple resource paths by separating them by comas. There...