Extended "ajaxvalidate", new attribute "fieldName" #569
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In some development scenarios, developers have to change input[id|name] in different web pages.
Current situations, enforce developers to make input-specific async server validation process for each input[id] or input[name].
Sometimes this server validation process is repetitive and they can not make/write their codes reusable.
By adding new "fieldName" property to "ajaxvalidate" custom validity rule core object, developers can make server codes more reusable and independent from client input[id|name].
Usage 1:
<input type='text'
id='Text1'
neme='UserID'
data-ajaxvalidate='path to asyc server validation handler'
data-ajaxvalidatefield='Username' />
Usage 2:
<input type='text'
id='Text1'
neme='UserID'
data-ajaxvalidate='{ url: "path to asyc server validation handler", fieldName: "Username"}' />
Contributor
Author
|
Hello.... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some development scenarios, developers have to change input[id|name] in different web pages.
Current situations, enforce developers to make input-specific async server validation process for each input[id] or input[name].
Sometimes this server validation process is repetitive and they can not make/write their codes reusable.
By adding new "fieldName" property to "ajaxvalidate" custom validity rule core object, developers can make server codes more reusable and independent from client input[id|name].
Usage 1:
Usage 2: