Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It would be useful to implement the hooks provided by the Clientside Validation module.
Comments
Comment #2
AohRveTPV CreditAttribution: AohRveTPV commentedHello. There have been very many requests to integrate directly with other contributed modules like Clientside Validation. We can't integrate with them all because it would make the code very complex and difficult to test/maintain. It's already overly complex. We ought to have a policy on this, but I think for the most popular modules (e.g. Drush), direct integration makes sense. For a module like Clientside Validation, I think a separate module (and separate Drupal.org) project which integrates the two would be ideal (assuming it's possible). So if a site maintainer wants to integrate Password Policy with Clientside Validation, they would install the integration module. That way the base Password Policy modules are kept simple and maintainable, and we don't have a proliferation of submodules to maintain. The maintenance of the integration modules can then be handled by those people who are most interested (you?).
That said, if it's possible to integrate indirectly, by changing the code in a way that doesn't assume any knowledge of Clientside Validation, we could certainly do that. Implementing hooks sounds direct.
Comment #3
AohRveTPV CreditAttribution: AohRveTPV commentedPlease re-open if you'd like to discuss further. Again, my current opinion is this would be best implemented in a separate project.
Comment #4
malcomio CreditAttribution: malcomio as a volunteer and at Capgemini commentedFair enough - for our project, we didn't have time to do this integration in a simple, generic way that would have been appropriate for a contrib module, and ended up implementing it in a slightly "hardcoded" way.