[1.0.x] JQuery form validation

Created on 28 December 2023, 9 months ago
Updated 13 August 2024, about 2 months ago

The JQuery form validation module enhances the form validation by entering the data into the json format to validate the form using the jQuery validation library . It helps to apply the validaion into the custom forms . You can access the test form after installing the module and apply the validation into the setting form

Project link

https://www.drupal.org/project/jquery_form_validation

📌 Task
Status

Closed: won't fix

Component

module

Created by

🇮🇳India karang

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @karang
  • 🇮🇳India vishal.kadam Mumbai

    Thank you for applying!

    Please read Review process for security advisory coverage: What to expect for more details and Security advisory coverage application checklist to understand what reviewers look for. Tips for ensuring a smooth review gives some hints for a smoother review.

    The important notes are the following.

    • If you have not done it yet, you should run phpcs --standard=Drupal,DrupalPractice on the project, which alone fixes most of what reviewers would report.
    • For the time this application is open, only your commits are allowed.
    • The purpose of this application is giving you a new drupal.org role that allows you to opt projects into security advisory coverage, either projects you already created, or projects you will create. The project status won't be changed by this application and no other user will be able to opt projects into security advisory policy.
    • We only accept an application per user. If you change your mind about the project to use for this application, or it is necessary to use a different project for the application, please update the issue summary with the link to the correct project and the issue title with the project name and the branch to review.

    To the reviewers

    Please read How to review security advisory coverage applications , Application workflow , What to cover in an application review , and Tools to use for reviews .

    The important notes are the following.

    • It is preferable to wait for a Code Review Administrator before commenting on newly created applications. Code Review Administrators will do some preliminary checks that are necessary before any change on the project files is suggested.
    • Reviewers should show the output of a CLI tool only once per application.
    • It may be best to have the applicant fix things before further review.

    For new reviewers, I would also suggest to first read In which way the issue queue for coverage applications is different from other project queues .

  • Status changed to Needs work 8 months ago
  • 🇮🇳India rushiraval

    Please solve phpcs Error

    FILE: jquery_form_validation/README.md
    ------------------------------------------------------------------------------------------
    FOUND 1 ERROR AND 1 WARNING AFFECTING 2 LINES
    ------------------------------------------------------------------------------------------
    5 | WARNING | [ ] Line exceeds 80 characters; contains 81 characters
    26 | ERROR | [x] Expected 1 newline at end of file; 0 found
    ------------------------------------------------------------------------------------------
    PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
    ------------------------------------------------------------------------------------------

    FILE: query_form_validation.settings.yml
    -----------------------------------------------------------------------------------------------
    FOUND 1 ERROR AFFECTING 1 LINE
    -----------------------------------------------------------------------------------------------
    9 | ERROR | [x] Expected 1 newline at end of file; 0 found
    -----------------------------------------------------------------------------------------------
    PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
    -----------------------------------------------------------------------------------------------

    FILE: jquery_form_validation/src/Form/TestValidationExampleForm.php
    -----------------------------------------------------------------------------------------------
    FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
    -----------------------------------------------------------------------------------------------
    98 | WARNING | #options values usually have to run through t() for translation
    -----------------------------------------------------------------------------------------------

    FILE: jquery_form_validation/src/Form/JQueryValidationSettingsForm.php
    -----------------------------------------------------------------------------------------------
    FOUND 0 ERRORS AND 6 WARNINGS AFFECTING 5 LINES
    -----------------------------------------------------------------------------------------------
    114 | WARNING | Unused variable $name_field.
    118 | WARNING | Unused variable $name_field.
    130 | WARNING | t() calls should be avoided in classes, use
    | | \Drupal\Core\StringTranslation\StringTranslationTrait and $this->t() instead
    138 | WARNING | t() calls should be avoided in classes, use
    | | \Drupal\Core\StringTranslation\StringTranslationTrait and $this->t() instead
    249 | WARNING | \Drupal calls should be avoided in classes, use dependency injection instead
    249 | WARNING | t() calls should be avoided in classes, use
    | | \Drupal\Core\StringTranslation\StringTranslationTrait and $this->t() instead
    -----------------------------------------------------------------------------------------------

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    I am changing priority as per Issue priorities .

  • Status changed to Closed: won't fix about 2 months ago
  • 🇮🇳India vishal.kadam Mumbai

    This thread has been idle, in the Needs work state with no activity for several months. Therefore, I am assuming that you are no longer pursuing this application, and I marked it as Closed (won't fix).

    If this is incorrect, and you are still pursuing this application, then please feel free to re-open it and set the issue status to Needs work or Needs review, depending on the current status of your code.

Production build 0.71.5 2024