You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am aware that there is typeUserAttrs which allow user to add custom attributes. However this needs to be done via code. Let's say that there is a requirement to use a validator such as http://parsleyjs.org which allows you to decoratively specify validation rules (data-parsley-*).
So, if by default a custom attribute field is available for all controls, this kind of requirements can be fulfilled. In my case if I had this option, I just have to keep the validation scripts in place and the person who design the form will have to learn the data-parsley-* options. He will just add those to our new "Custom element attribute" field. Then when the form is being filled by the end-user, those fields has all the validation custom attributes set and validation will get fired.
Also, a text area by default for every field can be provided to enter custom script? Can be useful in some cases?
Do you all think that this will be a valid use case?
The text was updated successfully, but these errors were encountered:
With typeUserEvents and typeUserAttrs it's possible to add a special attribute that enables users to add parsley options without knowing parsley. With some extra js you can provide a simple ui that let's then choose validators.
The same options can be used for the textarea that allow scripts, though if users have trouble assuming parsley options they will surely write page breaking js in the textarea.
Hello Kelvin,
I have created a custom attribute of checkbox using typeUserAttrs. At the time of editing of the checkbox , it is unchecked everytime even though the value of checkbox is true..
I am aware that there is typeUserAttrs which allow user to add custom attributes. However this needs to be done via code. Let's say that there is a requirement to use a validator such as http://parsleyjs.org which allows you to decoratively specify validation rules (data-parsley-*).
So, if by default a custom attribute field is available for all controls, this kind of requirements can be fulfilled. In my case if I had this option, I just have to keep the validation scripts in place and the person who design the form will have to learn the data-parsley-* options. He will just add those to our new "Custom element attribute" field. Then when the form is being filled by the end-user, those fields has all the validation custom attributes set and validation will get fired.
Also, a text area by default for every field can be provided to enter custom script? Can be useful in some cases?
Do you all think that this will be a valid use case?
The text was updated successfully, but these errors were encountered: