-
Notifications
You must be signed in to change notification settings - Fork 58
Validation Summary and preValidateFormElements #101
Comments
Hello, the To my understanding, the data of the Validation Summary is always there no matter what. So basically, I don't have the option that you are looking for. I might be missing that option but at this point it's not available. As for |
Thank you for responding. I see, I initially expected the validations in the Validation Summary to behave the same as those on the input fields (e.g. the options affecting them, like preValidateFormElements or Debounce) I found a short workaround for my problem described above to simply add: But I changed now my approach to the form validation to only show validations after the user pressed the submit button (because of wishes of the designer), where $validationSummary seems to provide a good way to achieve that. |
I might eventually add a new Global Options, something like I guess that I could add that in a few days when I get a little bit of free time. |
- Enhancement #100, add Global Option (errorMessageSeparator) for a Separator between error messages. - Enhancement #101, add Global Option (preValidateValidationSummary) to disable pre-validation in Validation Summary if need be. - Also found and fixed a problem with a try-catch throw javascript error in Custom Validation.
Added a new Global Option named Your code could look like this: var vs = new validationService({
hideErrorUnderInputs: true,
preValidateValidationSummary: false
}); |
Thanks a lot for the change! |
Because I want to display my validation messages summarized on the top of my page, instead of at the input field, I am trying to use Validation Summary for this purpose.
The problem is that the Validation Summary is already filled on page load, even though it should be deactivated in the global options:
// pre-validate all form elements (False by default)
preValidateFormElements: false
And of course I don't want to present the user with a huge list of Validation errors before he even started to type anything.
Is it intended that this preValidate option doesn't affect ValidationSummary?
Or maybe I am missing something?
Another approach for me would be to write my own summarization with DisplayErrorTo.
The text was updated successfully, but these errors were encountered: