Add a configuration option for exceptions to all forms selection

Open on Drupal.org →

Created on 23 December 2024, about 1 month ago

Problem/Motivation

Due to issues with jQuery validation, the number of forms that this module causes to break on our site is not insignificant. We could use the "Clientside Validation Enabled Forms" field if we choose to deselect the "Use Clientside Validation in all forms" checkbox. When dealing with a site of the complexity of ours, however, the number of forms we would have to explicitly identify to have the module validate would be significant. This configuration could go out of date when new entity types are added.

Thus, it would be ideal to be able to create an "Exceptions" form element that is available when the "Use Clientside Validation in all forms" is checked.

Proposed resolution

An "Exceptions" textfield added to the configuration form (`/admin/config/user-interface/clientside-validation`).
Any form id added to the "Exceptions" field, with one form id per line, results in the module not validating that form.

User interface changes

The "Exceptions" textfield would be visible when the "Use Clientside Validation in all forms" is checked.

The "Exceptions" field should have help text that describes the purpose.

Should there be data in the "Exceptions" textfield when the "Use Clientside Validation in all forms" is unchecked, that data should be removed when the configuration form is saved.

✨ Feature request

Status

Active

Version

4.0

Component

Code

Created by

🇺🇸United States skyriter

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Merge Requests

!23Add a configuration option for exceptions to all forms selection
Closed
🇺🇸United States skyriter
updated 10 days ago
!22Add a configuration option for exceptions to all forms selection
Closed
🇺🇸United States skyriter
updated 14 days ago

Comments & Activities

Issue created by @skyriter
Comment about 1 month ago →
🇺🇸United States skyriter
Comment 18 days ago →
🇺🇸United States skyriter
Comment 17 days ago →
🇺🇸United States skyriter
Comment 16 days ago →
🇺🇸United States swirt Florida
I like this idea very much. There have been a couple of sites I wanted to use this on, but validation was too greedy and broke a few forms. This addition would make it more useable for my use cases.
Comment 15 days ago →
🇺🇸United States skyriter
Merge request !22Draft: Resolve #3495738 "Add a configuration" → (Closed) created by skyriter
Merge request !23Issue #3495738: Excepted forms working → (Closed) created by skyriter
Comment 14 days ago →
System Message
skyriter → closed merge request !22
Pipeline finished with Success
14 days ago
Total: 159s
#392133
Comment 10 days ago →
System Message
skyriter → closed merge request !23
Comment 9 days ago →
🇺🇸United States skyriter
This issue was written without an understanding of what was already being done in https://www.drupal.org/project/clientside_validation/issues/2949540 ✨ Allow specific form ids for clientside validation Needs work .

As a result, I added code over there to satisfy the need to both include and exclude forms.

I think now that this issue would be better scoped to only exclude fields (though having spent some time trying to do just that, I am stumped on how to do it).

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024